Re: Usage of epoch in txid_current

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Usage of epoch in txid_current
Date: 2019-02-03 11:58:02
Message-ID: CAEepm=1B61wrvZ2OMCFtEKemjSbUA8bje0qAX5s82c6LOOuAkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 30, 2018 at 12:12 AM Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
> > On Tue, Jul 24, 2018 at 7:25 AM Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergei Kornilov 2019-02-03 12:33:38 Re: allow online change primary_conninfo
Previous Message Thomas Munro 2019-02-03 11:56:29 Re: Shared Memory: How to use SYSV rather than MMAP ?