> Is there a way to debug a PL/pgSQL function? It's behaving very
> Joel> It's crude, but you can output debugging statements w/ RAISE
> Joel> NOTICE or catch flawed assumptions by RAISE EXCEPTION.
Also try turning on query logging, so you can see in the postmaster
log the queries plpgsql is sending to the SQL engine. This is especially
helpful for catching unexpected substitutions or lack of substitutions
of plpgsql variables, as in Morgan Curley's recent problem over in
A volunteer to improve plpgsql's debugging/tracing facilities would
be favorably received...
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Howard Williams||Date: 2001-07-25 16:11:55|
|Subject: Can Postgres handle 2-phase commits ?|
|Previous:||From: Tom Lane||Date: 2001-07-25 15:38:04|
|Subject: Re: PostgreSQL 7.0 problem (may be bug?) |