Re: Should we add xid_current() or a int8->xid cast? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Should we add xid_current() or a int8->xid cast?
Date
Msg-id 30951.1585855230@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should we add xid_current() or a int8->xid cast?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2020-04-02 14:33:18 -0300, Alvaro Herrera wrote:
>> Hmm, for some reason I had it in my head that we would make these use an
>> "epoch/val" output format rather than raw uint64 values.

> Why would we do that? IMO the goal should be to reduce awareness of the
> 32bitness of normal xids from as many places as possible, and treat them
> as an internal space optimization.

If they're just int64s then you don't need special functions to do
things like finding the min or max in a column of them.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal: Expose oldest xmin as SQL function for monitoring
Next
From: David Steele
Date:
Subject: Re: backup manifests