From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Usage of epoch in txid_current |
Date: | 2018-07-10 03:32:34 |
Message-ID: | CAMsr+YGr+JefZH0_ZRhnKpm9F8mYbHyiUqF70UpoyBiqqNDvUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10 July 2018 at 10:40, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2018-07-10 10:32:44 +0800, Craig Ringer wrote:
> > On 10 July 2018 at 07:35, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2018-07-10 03:38:40 | Re: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled. |
Previous Message | Masahiko Sawada | 2018-07-10 03:03:33 | Re: Failure assertion in GROUPS mode of window function in current HEAD |