Thomas Hallgren <[EMAIL PROTECTED]> writes:
> I think this is a bad idea. PL/Java will use either shared memory or a
> socket to attach and as you already mentioned, when using C, a gdb
> will attach directly using the pid. I wouldn't be too surprised if
> Perl, Python, and PHP all have a similar solution and thus have no
> benefit from additions to the FE/BE protocol. IMO, debugging should be
> language specific and take place in a separate channel. There's no
> gain whatsoever mixing it with the FE/BE protocol.
It may well be that for plperl and friends we can kick the problem off
to language-specific debuggers --- indeed, one of the first things we
need to do is look at those to see what we can avoid reinventing.
But what of plpgsql?
Also, any solution of this type probably requires that the person doing
debugging have database superuser access (in fact, be logged directly
into the server machine as the postgres user). It'd be nice to have an
approach that could be used by non-superusers to debug their trusted-PL
functions.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
