From: | Marko Tiikkaja <marko(at)joh(dot)to> |
---|---|
To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | PL/pgSQL, RAISE and error context |
Date: | 2013-08-21 12:28:24 |
Message-ID: | 5214B268.3070303@joh.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
By default, PL/pgSQL does not print the error context of a RAISE
statement, for example:
=# create function foof() returns void as $$ begin raise exception
'foo'; end $$ language plpgsql;
CREATE FUNCTION
=# create function bar() returns void as $$ begin perform foof(); end $$
language plpgsql;
CREATE FUNCTION
=# select bar();
ERROR: foo
CONTEXT: SQL statement "SELECT foof()"
PL/pgSQL function "bar" line 1 at PERFORM
I find this extremely surprising, since if you raise the same exception
(or a DEBUG/NOTICE message) in multiple places, the error context is
missing valuable information. With a trivial change the last error
could be:
=# select bar();
ERROR: foo
CONTEXT: PL/pgSQL function "foof" line 1 RAISE
SQL statement "SELECT foof()"
PL/pgSQL function "bar" line 1 at PERFORM
which I find a lot better.
Thoughts?
Regards,
Marko Tiikkaja
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2013-08-21 12:40:24 | Re: Back-patch change in hashed DISTINCT estimation? |
Previous Message | Alexander Korotkov | 2013-08-21 12:04:36 | Re: CAST Within EXCLUSION constraint |