plpython tracebacks
This is a discussion on plpython tracebacks within the Pgsql Patches forums, part of the PostgreSQL category; --> URL added to TODO list. --------------------------------------------------------------------------- Neil Conway wrote: > P. Scott DeVos wrote: > > I'm on it. ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-18-2008, 01:44 AM
| ||||
| ||||
 Re: plpython tracebacks URL added to TODO list. --------------------------------------------------------------------------- Neil Conway wrote: > P. Scott DeVos wrote: > > I'm on it. > > Actually, don't worry about it -- I've made the corrections I had in > mind myself. Attached is a revised patch. On looking closer, I didn't > really like the way the patch accumulated the lines of the traceback: > AFAICS _PyString_Join() is not an "official" Python C API function (it's > not documented, at any rate), and besides it is cleaner and more > efficient to build up the traceback string in a StringInfo rather than > using Python lists and strings. > > The attached patch isn't quite finished: "No Traceback" when there is no > traceback information doesn't seem like the best message, I need to > update the regression tests and some comments, etc. But I plan to apply > something similar in substance to the attached patch to HEAD in the next > day or two, barring objections. > > -Neil > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster      |
Linear Mode
