On Wed, 2005-08-03 at 16:25 -0400, Tom Lane wrote:
> > The idea is to allow a PL/pgSQL exception to not automatically
> > rollback the work done by the current block.
>
> This fundamentally breaks the entire backend.
Yeah, but besides that, can you quick commit this to HEAD so I don't
have to keep track of it locally?
Just kidding.
> You do not have the
> option to continue processing after elog(ERROR); the (sub)transaction
> rollback is necessary to clean up inconsistent state.
Okay, I'll look at this more closely. Can you give me an example of
what can go wrong?
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
