From: | Raymond O'Donnell <rod(at)iol(dot)ie> |
---|---|
To: | Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Track a function |
Date: | 2009-02-14 16:51:48 |
Message-ID: | 4996F6A4.7080106@iol.ie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 14/02/2009 16:34, Carlos Henrique Reimer wrote:
> I've a plpgsql function that when called never ends and I would like to
> trace the internal function commands and see where is the problem.
>
> How can I trace what the function is doing?
You could insert RAISE NOTICE statements into your code, to show where
it is at that point.
You could also try the PL/PGSQL debugger, which comes as a contrib
module - pgAdmin III can act as a client for it,
Ray.
------------------------------------------------------------------
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
rod(at)iol(dot)ie
Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals
------------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Winter | 2009-02-14 21:16:54 | Problem with non-unique constraint names |
Previous Message | Andreas Kretschmer | 2009-02-14 16:49:59 | Re: Track a function |