Re: fdatasync performance problem with large number of DB files - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: fdatasync performance problem with large number of DB files
Date
Msg-id CA+hUKG+jfW0PFMQBp0Oyb3SDZAd6Uha8Hymc3A=sjTT9ocGYbA@mail.gmail.com
Whole thread Raw
In response to Re: fdatasync performance problem with large number of DB files  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Tue, Jun 22, 2021 at 5:01 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> On Fri, Jun 18, 2021 at 1:11 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > Thomas, could you comment on this ?
>
> Sorry, I missed that.  It is initially a confusing proposal, but after
> trying it out (that is: making recovery_init_sync_method PGC_SIGHUP
> and testing a scenario where you want to make the next crash use it
> that way and without the change), I agree.  +1 from me.

... and pushed.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Fix uninitialized copy_data var (src/backend/commands/subscriptioncmds.c)
Next
From: Amit Langote
Date:
Subject: Re: Deadlock risk while inserting directly into partition?