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

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: cca5507 <cca5507(at)qq(dot)com>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, 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-06-13 19:30:01
Message-ID: CAN4CZFOcppGJLKr6eoiqqfBofL2bCCz_cbVSg582pKzRgGoezA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you both for the review! After reviewing the issue again, I
agree that my 0002 was wrong.

0001 received a trivial rebase as there were no conflicts, and I
simply removed 0002 in favor of ChangAo Chen's thread.

Attachment Content-Type Size
0001-Enforce-minRecoveryPoint-check-regardless-of-archive.patch application/octet-stream 10.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-06-13 19:34:57 Re: Add explicit warnings about unsafe OAuth trace output for libpq
Previous Message Tom Lane 2026-06-13 15:56:39 Re: Change copyObject() to use typeof_unqual