Re: Making pg_rewind faster

John H <johnhyvr@gmail.com>

From: John H <johnhyvr@gmail.com>

To: Srinath Reddy Sadipiralla <srinath2133@gmail.com>

Cc: Robert Haas <robertmhaas@gmail.com>, wenhui qiu <qiuwenhuifx@gmail.com>, Japin Li <japinli@hotmail.com>, Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, Alexander Korotkov <aekorotkov@gmail.com>, Justin Kwan <justinpkwan@outlook.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>, vignesh ravichandran <admin@viggy28.dev>, "hlinnaka@iki.fi" <hlinnaka@iki.fi>

Date: 2025-10-21T23:14:55Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

pg_rewind: Skip copy of WAL segments generated before point of divergence
- 5173bfd0443e 19 (unreleased) landed
pg_rewind: Extend code detecting relation files to work with WAL files
- 6ae08d9583e9 19 (unreleased) landed
Split TESTDIR into TESTLOGDIR and TESTDATADIR
- c47885bd8b69 16.0 cited

Attachments

v11-0001-Avoid-copying-WAL-segments-before-divergence-to-.patch (application/octet-stream) patch v11-0001

Hi Srinath,

On Mon, Oct 20, 2025 at 9:36 PM Srinath Reddy Sadipiralla
<srinath2133@gmail.com> wrote:
> ...
> maybe something like this
> + "Expected WAL segment $corrupt_wal_seg to have later mtime
> on target than source after rewind as it was copied");
> + "Expected WAL segment $corrupt_wal_seg file sizes to be same
> between target and source after rewind as it was copied");
>

Made the changes and included the documentation update.

Thanks,
-- 
John Hsu - Amazon Web Services