Re: Proposal for debugging of server-side stored procedures

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Mark Cave-Ayland <m(dot)cave-ayland(at)webbased(dot)co(dot)uk>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal for debugging of server-side stored procedures
Date: 2006-06-09 16:01:11
Message-ID: 44899B47.2020305@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark Cave-Ayland wrote:

[snip]
> Perl seems a little more messy in that I can't find a documented C API to
> hook into the interpreter, but it looks as if it may be possible to cook
> something up with writing a new DB package [2] which uses XS call a C
> callback. The other issue is that unlike Python, the debug capability must
> be specified when creating the instance of interpreter rather than being
> able to enable/disable debugging on the fly so it may mean that two
> instances of the perl interpreter need to be maintained in memory - a
> standard instance and a debugging instance.
>
>

Debugging embedded perl has some significant challenges. You might find
it interesting to see what can be done in the most famous embedded
situation: mod_perl. See http://perl.apache.org/docs/1.0/guide/debug.html

using ptkdb might be nice ....

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2006-06-09 16:14:27 Re: That EXPLAIN ANALYZE patch still needs work
Previous Message A.M. 2006-06-09 16:01:07 Re: Fabian Pascal and RDBMS deficiencies in fully