Re: [BUG] Take a long time to reach consistent after pg_rewind

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: surya poondla <suryapoondla4(at)gmail(dot)com>
Cc: cca5507 <cca5507(at)qq(dot)com>, solai v <solai(dot)cdac(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG] Take a long time to reach consistent after pg_rewind
Date: 2026-11-19 17:46:48
Message-ID: CAHGQGwEXow3Sno_=w1heQob4no+FOMXWaz2919rif2a9rMr8+A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 25, 2026 at 2:48 AM surya poondla <suryapoondla4(at)gmail(dot)com> wrote:
> The latest patch looks good.

Attached is the updated version of the patch. It fixes the pg_rewind docs,
which still described pg_current_wal_insert_lsn() as the minimum
consistency LSN, to refer to pg_current_wal_flush_lsn() for a live primary.
I also revised the commit message and made some cosmetic changes.

Is it sufficient to apply this only to master, or we should backpatch it to
all supported versions?
I've also attached backpatch versions in case we decide to backpatch.

Regards,

--
Fujii Masao

Attachment Content-Type Size
v5-0001-pg_rewind-Fix-recovery-delays-at-WAL-page-boundar.patch application/octet-stream 7.6 KB
nocfbot-v5-0001-pg_rewind-Fix-recovery-delays-at-WAL-page-boundar-v15.patch application/octet-stream 7.7 KB
nocfbot-v5-0001-pg_rewind-Fix-recovery-delays-at-WAL-page-boundar-v18-v16.patch application/octet-stream 7.7 KB
nocfbot-v5-0001-pg_rewind-Fix-recovery-delays-at-WAL-page-boundar-v19.patch application/octet-stream 7.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-11-19 18:28:34 Re: A bug in recovery prefetcher, triggering asserts / FATAL: checkpoint request failed
Previous Message Andres Freund 2026-11-19 17:43:58 Re: Hash aggregate collisions cause excessive spilling