Re: PL/perl elog(ERROR) Does not Abort Transaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(dot)wheeler(at)iovation(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/perl elog(ERROR) Does not Abort Transaction
Date: 2012-05-11 16:39:03
Message-ID: 6880.1336754343@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David E. Wheeler" <david(dot)wheeler(at)iovation(dot)com> writes:
> HrmI've also just replicated it on CentOS 6.2 with Perl 5.10.1:

Interesting.

> Perhaps there is something funky in my configuration, though I tried a
> few different things and couldn't get it to change.

Yeah. If Bruce and I don't see it on a couple of configurations apiece,
and you do see it on two different machines, personal configuration
choices start to sound like a likely contributing factor. Could be
either PG configuration or Perl configuration (if there is any such
thing beyond installation-time decisions).

As for me, I was testing assert-enabled builds that were otherwise
entirely out-of-the-box, and I don't even know how to configure Perl.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-05-11 16:42:25 Re: [COMMITTERS] pgsql: Ensure age() returns a stable value rather than the latest value
Previous Message David E. Wheeler 2012-05-11 16:31:10 Re: PL/perl elog(ERROR) Does not Abort Transaction