Re: elog in 7.4
| От | Tom Lane |
|---|---|
| Тема | Re: elog in 7.4 |
| Дата | |
| Msg-id | 147.1095774278@sss.pgh.pa.us обсуждение |
| Ответ на | elog in 7.4 (Laszlo Hornyak <kocka@forgeahead.hu>) |
| Ответы |
Re: elog in 7.4
|
| Список | pgsql-hackers |
Laszlo Hornyak <kocka@forgeahead.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
В списке pgsql-hackers по дате отправления: