Re: Usage of epoch in txid_current - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Usage of epoch in txid_current
Date
Msg-id CAMsr+YGr+JefZH0_ZRhnKpm9F8mYbHyiUqF70UpoyBiqqNDvUw@mail.gmail.com
Whole thread Raw
In response to Re: Usage of epoch in txid_current  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 10 July 2018 at 10:40, Andres Freund <andres@anarazel.de> wrote:
On 2018-07-10 10:32:44 +0800, Craig Ringer wrote:
> On 10 July 2018 at 07:35, Thomas Munro <thomas.munro@enterprisedb.com>
> wrote:
>
> >
> > I played around with this idea yesterday.  Experiment-grade patch
> > attached.  Approach:
> >
> > 1.  Introduce a new type BigTransactionId (better names welcome).
> >
>
> txid_current() should be changed to BigTransactionId too. It's currently
> bigint.

That's quite a bit more work though, no? We'd have to introduce a new
SQL level type (including operators).  As I said nearby, I think that's
a good idea, but I don't see any sort of benefit of forcing those
patches to be done at once.

Yeah. You're right. One step at a time.


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

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Failure assertion in GROUPS mode of window function in current HEAD
Next
From: Etsuro Fujita
Date:
Subject: Re: Expression errors with "FOR UPDATE" and postgres_fdw with partitionwise join enabled.