Re: BUG #14639: Different xmin values in a transaction

From: Andres Freund <andres(at)anarazel(dot)de>
To: ray(dot)warren(at)artsalliancemedia(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14639: Different xmin values in a transaction
Date: 2017-05-02 16:13:20
Message-ID: 20170502161320.lbxb2sj6knpwzx7k@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2017-05-02 15:57:39 +0000, ray(dot)warren(at)artsalliancemedia(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ray Warren 2017-05-02 16:25:33 Re: BUG #14639: Different xmin values in a transaction
Previous Message ray.warren 2017-05-02 15:57:39 BUG #14639: Different xmin values in a transaction