Re: Debugging Server Code - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: Debugging Server Code
Date
Msg-id 45F85369.1070809@commandprompt.com
Whole thread Raw
In response to Debugging Server Code  (Kenneth Downs <ken@secdat.com>)
Responses Re: Debugging Server Code  (Klint Gore <kg@kgb.une.edu.au>)
List pgsql-general
Kenneth Downs wrote:
> I'm guessing that there is no step-wise debugger for pgsql.  If there
> is, then glory be and call me a dummy for not R'ing TFM.
> In fact, I've never heard of a step-wise debugger for any DB server, am
> I wrong?
>
> As I grovel through some plPerl code in a statement level trigger that
> depends on an array of variables, I wonder if the lack of such a
> debugger can be considered one of the biggest impediments to larger
> adoption of server-side code.  I don't mean to be facetious here, how
> many serious and powerful programmers do you know who don't depend
> heavily on a good debugger to step through the code and find the nasty
> parts?

Every one that properly uses server side code ;)


> Anyway, just a thought.

It certainly would be great. IIRC there is actually one for plpgsql over
at pgfoundry.

Joshua D. Drake


>
> We now return to our regularly scheduled mailing list...
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org/
>


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/


pgsql-general by date:

Previous
From: Randall Smith
Date:
Subject: Re: quoted identifier behaviour
Next
From: "Adam Rich"
Date:
Subject: Re: Debugging Server Code