Re: Disable startup progress timeout during standby WAL replay

From: Aidar Imamov <imamovaj22(at)gmail(dot)com>
To: Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Disable startup progress timeout during standby WAL replay
Date: 2026-10-26 13:41:42
Message-ID: 8FE706AA-BFC2-4B0D-B96C-950425935840@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> +1 for splitting them. I suggest keeping Fujii-san’s standby timeout
> fix in this thread and moving the recovery-conflict issue to a
> separate thread and patch. That should allow the two changes to be
> reviewed, tested, and considered for backpatching independently.

I moved it out of this thread. It now has its own thread and CF entry:

https://www.postgresql.org/message-id/flat/1D46953B-2FE9-4611-9B46-FAE91184AE99(at)gmail(dot)com

https://commitfest.postgresql.org/patch/7521

+1, keeping it apart means this thread stays focused on Fujii's change,
and the other fix can get proper review plus a backpatch discussion of
its own.

I've re-attached Fujii's v1 patch to this message.
So the CF bot reports the correct status in the UI.
Nothing else changed in the patch from my side.

Regards,
Aidar Imamov



In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message David Geier 2026-10-26 13:32:20 Re: [PATCH v1] Batch B-tree TIDs when building a bitmap