Hackers,
Shouldn't a call to elog(NOTICE) invalidate the current tranaction?
david=# begin; BEGIN Time: 0.178 ms david=# do language plperl $$ elog(ERROR, 'foo')$$; ERROR: foo at line
1. CONTEXT: PL/Perl anonymous code block david=# select true; bool ------ t (1 row)
Time: 0.203 ms
The docs say:
> ERROR raises an error condition; if this is not trapped by the surrounding Perl code, the error propagates out to the
callingquery, causing the current transaction or subtransaction to be aborted.
So I'm surprised that the transaction is not aborted. Bug?
David
