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

From Thomas Munro
Subject Re: Usage of epoch in txid_current
Date
Msg-id CAEepm=1B61wrvZ2OMCFtEKemjSbUA8bje0qAX5s82c6LOOuAkg@mail.gmail.com
Whole thread Raw
In response to Re: Usage of epoch in txid_current  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: Usage of epoch in txid_current  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Fri, Nov 30, 2018 at 12:12 AM Dmitry Dolgov <9erthalion6@gmail.com> wrote:
> > On Tue, Jul 24, 2018 at 7:25 AM Thomas Munro <thomas.munro@enterprisedb.com> wrote:
> > Here's a new version.  I did some cosmetic clean-up, and I dropped the
> > changes to pg_controldata output, replication epoch/xid processing
> > code and various similar non-essential changes.  For this patch I want
> > just the new type + next xid generator + appropriate conversions.
> >
> > I propose that we get this committed early in the cycle.  That'd
> > maximise testing time in the tree, fix the bug identified by Amit, and
> > leave plenty of time for later patches to use FullTransactionId in
> > more places as appropriate.
>
> Then probably it's the good time to do so. Any opinions or more reviews here?
> I'll move it to the next CF for now.

If there are no objections, I'm planning to do a round of testing and
commit this shortly.

-- 
Thomas Munro
http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Shared Memory: How to use SYSV rather than MMAP ?
Next
From: Sergei Kornilov
Date:
Subject: Re: allow online change primary_conninfo