Re: Back-patch of: avoid multiple hard links to same WAL file after a crash - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Back-patch of: avoid multiple hard links to same WAL file after a crash
Date
Msg-id Z86E0BhjiiZQURvL@paquier.xyz
Whole thread Raw
In response to Re: Back-patch of: avoid multiple hard links to same WAL file after a crash  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Mon, Mar 10, 2025 at 02:25:28PM +0900, Michael Paquier wrote:
> I am attaching a full set of patches for v14 and v13 that can be used
> for these tests.  WDYT?

And I forgot to mention that I've checked both v14 and v13, where I
have noticed the two patterns "invalid magic number 0000 in log
segment X, offset 0" and "unexpected pageaddr X in log segment Y" as
LOG and DEBUG entries.

These are gone once the patches are applied on both branches.  Just
set max_wal_size and min_wal_size (128MB here) low enough with a
standby doing archive recovery, and bulk-load WAL on the primary to
accelerate the reproduction of the problem.  It takes a couple of
minutes to have these show up with the unpatched branches.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Shlok Kyal
Date:
Subject: Re: Restrict copying of invalidated replication slots
Next
From: Bertrand Drouvot
Date:
Subject: Re: Log connection establishment timings