Re: Regression tests fail once XID counter exceeds 2 billion

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Regression tests fail once XID counter exceeds 2 billion
Date: 2012-08-17 00:09:01
Message-ID: 20120817000900.GF30286@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 16, 2011 at 07:08:27PM -0500, Tom Lane wrote:
> I wrote:
> > Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> >> We need a function called transactionid_current() so a normal user can write
>
> >> select virtualtransaction
> >> from pg_locks
> >> where transactionid = transactionid_current()
>
> >> and have it "just work".
>
> > That would solve that one specific use-case. The reason I suggested
> > txid_from_xid is that it could also be used to compare XIDs seen in
> > tuples to members of a txid_snapshot, which is not possible now.
>
> BTW, a pgsql-general question just now made me realize that
> txid_from_xid() could have another use-case too. Right now, there are
> no inequality comparisons on XIDs, which is necessary because XIDs in
> themselves don't have a total order. However, you could
>
> ORDER BY txid_from_xid(xmin)
>
> and it would work, ie, give you rows in their XID order. This could be
> useful for finding the latest-modified rows in a table, modulo the fact
> that it would be ordering by transaction start time not commit time.

Added to TODO:

Add function to allow easier transaction id comparisons

http://archives.postgresql.org/pgsql-hackers/2011-11/msg00786.php

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dickson S. Guedes 2012-08-17 00:44:22 Re: CREATE SCHEMA IF NOT EXISTS
Previous Message Bruce Momjian 2012-08-16 23:38:44 Re: Avoiding shutdown checkpoint at failover