Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>
Subject: Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound
Date: 2023-10-01 23:33:39
Message-ID: CAH2-WzkVw6RXaQzAubyRbPMvwouV1TphhhTSdbDktGD1ARkRSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 1, 2023 at 11:46 AM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> What is the status of this patch discussion now? It had been set as
> Ready for Committer for some months. Do these recent discussions
> invalidate that? Does it need more discussion?

I don't think that recent discussion invalidated anything. I meant to
follow-up on investigating the extent to which anything could hold up
OldestMXact without also holding up OldestXmin/removable cutoff, but
that doesn't seem essential.

This patch does indeed seem "ready for committer". John?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-10-02 00:01:22 Re: Making the subquery alias optional in the FROM clause
Previous Message Peter Geoghegan 2023-10-01 23:20:42 Re: pgstatindex vs. !indisready