From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: xmin increasing within a transaction block? |
Date: | 2017-11-06 13:29:30 |
Message-ID: | 20171106132930.jegnqzoswhdcsbl2@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On 2017-11-06 10:36:06 +0100, Luca Ferrari wrote:
> Hi all,
> I suspect this has a trivial explaination, but this is what I'm experiencing:
>
> > CREATE TABLE foo( i int );
> > BEGIN;
> * > INSERT INTO foo(i) VALUES( 1 );
> * > INSERT INTO foo(i) VALUES( 2 );
> * > SELECT xmin, cmin, xmax, cmax, i FROM foo;
> xmin | cmin | xmax | cmax | i
> ------+------+------+------+---
> 2466 | 0 | 0 | 0 | 1
> 2467 | 1 | 0 | 1 | 2
> (2 rows)
>
> * > SELECT txid_current();
> txid_current
> --------------
> 2465
> (1 row)
>
>
> Why is xmin greater than the current transaction id (and most notably
> not "fixed")?
> What am I missing here?
> I'm running 9.6.5.
That doesn't look like plain postgres behaviour to me. Any chance you're
using a pooler in statement mode in front of postgres?
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Sachin Kotwal | 2017-11-06 13:33:08 | Re: Naming conventions for column names |
Previous Message | Vikas Sharma | 2017-11-06 13:28:45 | Postgresql 9.3 service doesn't start on RedHat Linux 6.8 |