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

From Michael Paquier
Subject Re: avoid multiple hard links to same WAL file after a crash
Date
Msg-id YsTP5J55dOQAYzbQ@paquier.xyz
Whole thread Raw
In response to Re: avoid multiple hard links to same WAL file after a crash  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On Tue, Jul 05, 2022 at 09:58:38AM -0700, Nathan Bossart wrote:
> Thanks!  I wonder if we should add a comment in writeTimeLineHistoryFile()
> about possible concurrent use by a WAL receiver and the startup process and
> why that is okay.

Agreed.  Adding an extra note at the top of the routine would help in
the future.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: should check interrupts in BuildRelationExtStatistics ?
Next
From: Tom Lane
Date:
Subject: Re: Doc about how to set max_wal_senders when setting minimal wal_level