Re: [PATCH] bigint txids vs 'xid' type, new txid_recent(bigint) => xid

From: Greg Stark <stark(at)mit(dot)edu>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] bigint txids vs 'xid' type, new txid_recent(bigint) => xid
Date: 2016-08-16 12:58:06
Message-ID: CAM-w4HPCAxCGTj-LHiyKtiqqNZTBJ9iTng2HheZ_xLaN1psWQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 16, 2016 at 10:15 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> I'm surprised the 32-bit xid was ever exposed to the user, rather than a
> 64-bit epoch-extended xid.

Once upon a time we didn't have epoch counting at all.

I don't think it would be a bad idea to clean up everything to do with
xids so that everything user-facing is epoch-aware. Of course you
don't always have the epoch but if we're careful about where users can
see xids they should never see an xid from an old epoch. That could be
a problem for internal tools like pageinspect or xlogdump but
shouldn't be a problem for any real production api.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-16 13:37:54 Re: [RFC] Change the default of update_process_title to off
Previous Message Greg Stark 2016-08-16 12:53:33 Re: PSA: Systemd will kill PostgreSQL