Re: InstallXLogFileSegment() vs concurrent WAL flush - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: InstallXLogFileSegment() vs concurrent WAL flush
Date
Msg-id CA+hUKG+bk2BO282C1DaZ7PLUyxkShNLc2iPyiHEWhR=gS4gmpA@mail.gmail.com
Whole thread Raw
In response to Re: InstallXLogFileSegment() vs concurrent WAL flush  (Yugo NAGATA <nagata@sraoss.co.jp>)
Responses Re: InstallXLogFileSegment() vs concurrent WAL flush
List pgsql-hackers
On Fri, Feb 2, 2024 at 12:56 PM Yugo NAGATA <nagata@sraoss.co.jp> wrote:
> On Fri, 2 Feb 2024 11:18:18 +0100
> Thomas Munro <thomas.munro@gmail.com> wrote:
> > One simple way to address that would be to make XLogFileInitInternal()
> > wait for InstallXLogFileSegment() to finish.  It's a little
>
> Or, can we make sure the rename is durable by calling fsync before
> returning the fd, as a patch attached here?

Right, yeah, that works too.  I'm not sure which way is better.



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: POC: Extension for adding distributed tracing - pg_tracing
Next
From: Heikki Linnakangas
Date:
Subject: Re: XLog size reductions: smaller XLRec block header for PG17