Re: plpgsql debugging - Mailing list pgsql-hackers

From Andreas Pflug
Subject Re: plpgsql debugging
Date
Msg-id 3F5CAAFA.9000203@pse-consulting.de
Whole thread Raw
In response to Re: plpgsql debugging  (Richard Huxton <dev@archonet.com>)
Responses Re: plpgsql debugging  (Richard Huxton <dev@archonet.com>)
List 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




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: plpgsql doesn't coerce boolean expressions to boolean
Next
From: "luke"
Date:
Subject: pgsql vc++|win32