| From: | Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Clarify the behavior of the system when approaching XID wraparound |
| Date: | 2023-10-02 09:15:09 |
| Message-ID: | CALT9ZEGTD3dpP9DoZO-8_zCKsSZzghmJoHbuWT6KRA4Dqb6vtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
On Mon, 2 Oct 2023 at 03:34, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> 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
FWIW I think the patch is still in good shape and worth to be committed.
Regards,
Pavel Borisov
Supabase
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2023-10-02 09:19:29 | Re: Show various offset arrays for heap WAL records |
| Previous Message | Drouvot, Bertrand | 2023-10-02 08:53:22 | Re: Add a new BGWORKER_BYPASS_ROLELOGINCHECK flag |