From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Laszlo Hornyak <kocka(at)forgeahead(dot)hu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: elog in 7.4 |
Date: | 2004-09-21 13:44:38 |
Message-ID: | 147.1095774278@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Laszlo Hornyak <kocka(at)forgeahead(dot)hu> writes:
> I am implementing a java language handler. If unrecoverable error occurs,
> it needs to send a signal to the java process, so it can stop the
> execution of the stored procedure, otherwise it would stay in inconsystent
> state.
Well, an elog callback is certainly the wrong place for that. Even if
it looked to see whether the elog call was ERROR or not, an ERROR is no
longer necessarily unrecoverable --- it might be caught inside a plpgsql
exception block, for example, and not really be an error at all from the
perspective of calling code.
The right way would be to use PG_TRY to catch the exception as it
propagates out to your own level of control.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-09-21 13:44:43 | Re: SSL Support |
Previous Message | Sudhakar Kurumella | 2004-09-21 12:58:25 | Re: psql: FATAL: Password authentication failed for |