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 necessary to clean up inconsistent state.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
