| From: | Ludwig Lim <lud_nowhere_man(at)yahoo(dot)com> |
|---|---|
| To: | Oliver Vecernik <vecernik(at)aon(dot)at> |
| Cc: | PostgreSQL Mailing List <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: plpgsql: debugging |
| Date: | 2003-01-24 07:41:10 |
| Message-ID: | 20030124074110.57736.qmail@web80312.mail.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
--- Oliver Vecernik <vecernik(at)aon(dot)at> wrote:
> Hi,
>
> Searching Google I found a thread in July 2001
> concerning the facilities
> for debugging plpgsql functions. The actual answer
> was: it should be
> improved.
>
> What is the best way to debug a plpgsql function?
>
> Oliver
This may not be the best way since its a bit
crude. Try using RAISE NOTICE every now then to
monitor the values of variables in the screen and
record it in log file.
Example :
RAISE NOTICE ''Initial value of variable =
%'',v_variable;
/* Do some computation ... */
RAISE NOTICE ''Value of variable after operation =
%'',v_variable;
hope that helps,
ludwig
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Gamache | 2003-01-24 07:58:54 | Race condition w/ FIFO Queue reappears! |
| Previous Message | David Durst | 2003-01-24 07:13:04 | Re: Scheduling Events? |