Re: [PATCH] Transaction traceability - txid_status(bigint) - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [PATCH] Transaction traceability - txid_status(bigint)
Date
Msg-id CAMsr+YE-sTSpeoDioWw6CO_W6ny63NzrfW_GoW1P0N4JTxX0CQ@mail.gmail.com
Whole thread Raw
In response to [PATCH] Transaction traceability - txid_status(bigint)  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [PATCH] Transaction traceability - txid_status(bigint)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 20 August 2016 at 21:24, Craig Ringer <craig@2ndquadrant.com> wrote:
Hi all

Following on from 

bigint txids vs 'xid' type, new txid_recent(bigint) => xid


Ahem. Forgot to squash in a fixup commit. Updated patch of txid_status(bigint) attachd.

A related patch follows, adding a new txid_current_ifassigned(bigint) function as suggested by Jim Nasby. It's usefully connected to txid_status() and might as well be added at the same time.

Since it builds on the same history I've also attached an updated version of txid_recent(bigint) now called txid_convert_ifrecent(bigint), per the above-linked thread.

Finally, and not intended for commit, is a useful test function I wrote to cause extremely rapid xid wraparound, bundled up into a src/test/regress test case. txid_incinerate() can jump the server about UINT32/2 xids in ~2 seconds if fsync is off, making it handy for testing.  Posting so others can use it for their own test needs later and because it's useful for testing these patches that touch on the xid epoch.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: LSN as a recovery target
Next
From: Craig Ringer
Date:
Subject: Re: [PATCH] bigint txids vs 'xid' type, new txid_recent(bigint) => xid