On Thu, May 10, 2012 at 05:27:26PM -0700, David E. Wheeler wrote:
> On May 10, 2012, at 5:20 PM, Bruce Momjian wrote:
>
> >>
> >> Shouldn't a call to elog(NOTICE) invalidate the current tranaction?
> >
> > I assume you mean elog(ERROR)?
>
> Yes, sorry.
>
> > Well, git head show an error:
> >
> > test=> begin;
> > BEGIN
> > test=> do language plperl $$ elog(ERROR, 'foo')$$;
> > ERROR: foo at line 1.
> > CONTEXT: PL/Perl anonymous code block
> > test=> select true;
> > ERROR: current transaction is aborted, commands ignored until end of
> > transaction block
>
> Interesting. My build (from source):
>
> PostgreSQL 9.1.3 on x86_64-apple-darwin11.3.0, compiled by
> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658)
> (LLVM build 2336.1.00), 64-bit
> (1 row)
OK, still an abort on 9.1.X head:
$ psql test
psql (9.1.3)
Type "help" for help.
test=> begin;
BEGIN
test=> do language plperl $$ elog(ERROR, 'foo')$$;
ERROR: foo at line 1.
CONTEXT: PL/Perl anonymous code block
test=> select true;
ERROR: current transaction is aborted, commands ignored until end of
transaction block
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
