Apologies - new list user, hit reply not reply all :-/
korry.douglas wrote:
>
>> Yeah, I think so. The PL/pgSQL debugger was part of a list of 14-15
>> features I gave Charles Babcock; not sure why he liked that one, but
>> he did.
>>
>> Last I talked to Korry, it was ready to go. No?
>>
> If by "ready to go" you mean "has been exercised by a mess o' people", no.
> If by "ready to go" you mean "has been tested by a few people and
> compiled on a few platforms", that's where we are now - I would like to
> see some more testing (especially on platforms other than Windows,
> Linux, and OS X).
>
> The core of the debugger has been in use for quite some time, but I had
> to strip out a lot of EDB-specific code and I'd like to see that the
> result (the open-source version at pgFoundry) holds up well on other
> platforms.
> Josh, any chance you could try it out on Solaris?
Looks great, and I'll be testing it shortly, but can I ask:
1. For 8.3 are we talking pgFoundry / contrib / core?
2. Would you accept an additional mode: logging?
It would be useful to be able to embed a couple of statements in
application to code to turn logging on/off at specific points in real
usage situations. Nothing as fancy as log4j/c/perl etc. just (timestamp,
facility, level, message) to a table.
SET plpgsql.logging_facilities='any,list,or,asterisk'
SET plpgsql.logging_levels='DEBUG,INFO'
SET plpgsql.logging_tablename='foo'
Hmm - tricky bit would presumably be the logging statement itself. Would
it be possible to keep the overheads low enough without interfering with
plpgsql itself?
-- Richard Huxton Archonet Ltd