Re: Bug? pg_rewind produces unusable but starting database with standby recovery

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: cca5507 <cca5507(at)qq(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bug? pg_rewind produces unusable but starting database with standby recovery
Date: 2026-08-25 05:51:42
Message-ID: A722F5E1-D231-4E72-ACDD-2F48FC817F8C@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Zsolt,

On Sat, Jun 13, 2026 at 10:30 PM Zsolt Parragi wrote:
> 0001 received a trivial rebase as there were no conflicts, and I
> simply removed 0002 in favor of ChangAo Chen's thread.

Sorry for the delayed follow-up. I rechecked the remaining patch against
the current master. My concern was entirely about the former 0002, so
removing it resolves it. 0001 still looks correct to me, and the test
covers both refusing to start when the required WAL is unavailable and
successful recovery from the archive.

The CF entry can be marked Ready for Committer.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Chao Li 2026-08-25 05:51:24 Reduce logical WAL volume with restricted replication slots