Re: plpgsql debugging

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql debugging
Date: 2003-09-08 16:14:50
Message-ID: 3F5CAAFA.9000203@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Richard Huxton wrote:

>Actually, a simple trace ability would be a huge step forward. It'd save me
>dotting RAISE statements around my functions while I write them.
>
Sounds bloody familiar... :-(

> Even the ability to add DEBUG statements that checked some global flag before firing
>would be very useful (to me at least).
>
>
I could imagine a DEBUG .... which works like RAISE NOTICE with checking
for a set variable, and ASSERT which works like RAISE ERROR.

Does anybody expect keyword conflicts from this?

Regards,
Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message luke 2003-09-08 16:15:49 pgsql vc++|win32
Previous Message Andrew Dunstan 2003-09-08 16:10:27 Re: [HACKERS] plpgsql doesn't coerce boolean expressions to boolean