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+hUKGLkoO6i2qoP6u9uKPx8SL4MGzMnT+xQJ+p_x3FggH1Z8A@mail.gmail.com
Whole thread Raw
In response to Re: fdatasync performance problem with large number of DB files  (Paul Guo <guopa@vmware.com>)
Responses Re: fdatasync performance problem with large number of DB files
Re: fdatasync performance problem with large number of DB files
List pgsql-hackers
On Thu, Mar 18, 2021 at 8:52 PM Paul Guo <guopa@vmware.com> wrote:
> About the syncfs patch, my first impression on the guc name sync_after_crash
> is that it is a boolean type. Not sure about other people's feeling. Do you guys think
> It is better to rename it to a clearer name like sync_method_after_crash or others?

Works for me.  Here is a new version like that, also including the
documentation change discussed with Fujii-san, and a couple of
cosmetic changes.

Attachment

pgsql-hackers by date:

Previous
From: Masahiro Ikeda
Date:
Subject: Re: make the stats collector shutdown without writing the statsfiles if the immediate shutdown is requested.
Next
From: Magnus Hagander
Date:
Subject: Re: hint Consider using pg_file_read()