Re: Making pg_rewind faster

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: John H <johnhyvr@gmail.com>

Cc: Srinath Reddy Sadipiralla <srinath2133@gmail.com>, Robert Haas <robertmhaas@gmail.com>, wenhui qiu <qiuwenhuifx@gmail.com>, Japin Li <japinli@hotmail.com>, 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-24T08:38:37Z

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

v13-0001-Avoid-copying-WAL-segments-before-divergence-to-.patch (text/x-diff) patch v13-0001

On Fri, Oct 24, 2025 at 04:56:33PM +0900, Michael Paquier wrote:
> I was just wondering about some queries on the new standby once we are
> done with the rewind.  But after sleeping on it, I'd be happy with
> just the set of tests we have: the debug output checks, the size
> checks pre and post-rewind, and no mtime.

So, I am coming down to the attached (minus the commit message) after
more edits and adjustments.  It's Friday evening here, and I am not
planning to do more today and to take bets on the buildfarm, even if
the CI is OK.
--
Michael