Postgres Pro
Downloads
Home   >   mailing lists

Re: [BUGS] BUG #14639: Different xmin values in a transaction - Mailing list pgsql-bugs

From Andres Freund
Subject Re: [BUGS] BUG #14639: Different xmin values in a transaction
Date
Msg-id 20170502161320.lbxb2sj6knpwzx7k@alap3.anarazel.de
Whole thread Raw
In response to [BUGS] BUG #14639: Different xmin values in a transaction  (ray.warren@artsalliancemedia.com)
Responses Re: [BUGS] BUG #14639: Different xmin values in a transaction  (Ray Warren <Ray.Warren@artsalliancemedia.com>)
List pgsql-bugs
Tree view 
On 2017-05-02 15:57:39 +0000, ray.warren@artsalliancemedia.com wrote:
> Under certain conditions inserts in the same transaction are getting
> different xmin values.
> A reproducible example is below. I can work around it but I think this is a
> bug.

That's to be expected if you use savepoints (and EXCEPTION blocks use
those internally).  Why do you care about xmin value?

Greetings,

Andres Freund


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: ray.warren@artsalliancemedia.com
Date:
Subject: [BUGS] BUG #14639: Different xmin values in a transaction
Next
From: Ray Warren
Date:
Subject: Re: [BUGS] BUG #14639: Different xmin values in a transaction