| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: PL/perl elog(ERROR) Does not Abort Transaction |
| Date: | 2012-05-11 17:19:15 |
| Message-ID: | 8223.1336756755@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)justatheory(dot)com> writes:
> On May 11, 2012, at 9:51 AM, David E. Wheeler wrote:
>> \set ON_ERROR_ROLLBACK interactive
>>
>> So I guess it transparently rolls back a savepoint for the previous statement. I had forgotten I turned that on. Apologies for the noise.
Ah-hah.
> OTOH, might it be useful to have psql show some sort of status message when it does this?
The same occurred to me, but after more thought I think it'd just be
horribly annoying after a short time. People who have this set will
(or should, anyway) be expecting errors to be nonfatal to their
transactions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-05-11 17:20:26 | Re: WalSndWakeup() and synchronous_commit=off |
| Previous Message | Kevin Grittner | 2012-05-11 17:16:12 | Re: Gsoc2012 idea, tablesample |