From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Andres Freund <andres@anarazel.de>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Petr Jelinek <petr@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Thomas Munro <thomas.munro@gmail.com>
Subject: Re: Snapbuild woes followup
Date: Thu, 4 Feb 2021 12:23:53 -0300
Message-ID: <20210204152353.GA6117@alvherre.pgsql> (raw)
In-Reply-To: <20210125204813.iavrp2seuaaysmxa@alap3.anarazel.de>
On 2021-Jan-25, Andres Freund wrote:
> See attached patch...
Looks good to me.
I was wondering if there would be a point in using a FullTransactionId
instead of an unadorned one. I don't know what's the true risk of
an Xid wraparound occurring here, but it seems easier to reason about.
But then that's probably a larger change to make all of snapbuild use
FullTransactionIds, so not for this patch to worry about.
--
Álvaro Herrera 39°49'30"S 73°17'W
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, andres@anarazel.de, hlinnaka@iki.fi, petr@2ndquadrant.com, thomas.munro@gmail.com
Subject: Re: Snapbuild woes followup
In-Reply-To: <20210204152353.GA6117@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox