Re: [PATCH] Transaction traceability - txid_status(bigint)

Petr Jelinek <petr@2ndquadrant.com>

From: Petr Jelinek <petr@2ndquadrant.com>
To: Craig Ringer <craig@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Jim Nasby <Jim.Nasby@bluetreble.com>
Date: 2016-08-23T08:02:16Z
Lists: pgsql-hackers
On 23/08/16 02:55, Craig Ringer wrote:
> On 23 August 2016 at 01:03, Robert Haas <robertmhaas@gmail.com
> <mailto:robertmhaas@gmail.com>> wrote:
>
>
>
>     I think you should use underscores to separate all of the words
>     instead of only some of them.
>
>
> ifassigned => if_assigned
>
> ifrecent=> if_recent
>
> Updated patch series attached. As before, 0-4 intended for commit, 5
> just because it'll be handy to have around for people doing wraparound
> related testing.

I guess you mean 0-3 for commit and 4 is just handy?

 From the point of code this patch seems good to me.

I do wonder about the 3rd patch though. I wonder if it would not be 
better to have the opposite function instead - converting xid to txid as 
that will always work and does not have to have the NULL case and would 
be simpler in terms of code.

-- 
   Petr Jelinek                  http://www.2ndQuadrant.com/
   PostgreSQL Development, 24x7 Support, Training & Services


Commits

  1. Add a txid_status function.

  2. Track the oldest XID that can be safely looked up in CLOG.