Tom, is there other way in pg 7.4 than backporting PG_TRY? It seems a lot of work.
Thanks, Laszlo On Tue, 21 Sep 2004, Tom Lane wrote: > Laszlo Hornyak <[EMAIL PROTECTED]> 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 > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings > ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
