This was motivated by the SELECT INTO EXACT discussion at
http://archives.postgresql.org/pgsql-patches/2005-07/msg00559.php.
The idea is to allow a PL/pgSQL exception to not automatically rollback
the work done by the current block. The benefit is that exception
handling can be used as a program
Matt Miller [EMAIL PROTECTED] writes:
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. You do not have the
option to continue processing after elog(ERROR); the (sub)transaction
rollback is
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
Matt Miller [EMAIL PROTECTED] writes:
On Wed, 2005-08-03 at 16:25 -0400, Tom Lane wrote:
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
