| From: | "David E(dot) Wheeler" <david(dot)wheeler(at)iovation(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: PL/perl elog(ERROR) Does not Abort Transaction |
| Date: | 2012-05-11 00:27:26 |
| Message-ID: | B9C0E3A6-EA17-4F7B-9C34-35D047330272@iovation.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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)
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2012-05-11 00:38:43 | Re: Gsoc2012 idea, tablesample |
| Previous Message | Bruce Momjian | 2012-05-11 00:20:46 | Re: PL/perl elog(ERROR) Does not Abort Transaction |