Re: fdatasync performance problem with large number of DB files

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>
To: Paul Guo <guopa@vmware.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Tom Lane <tgl@sss.pgh.pa.us>, Michael Brown <michael.brown@discourse.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-18T10:19:13Z
Lists: pgsql-hackers

Attachments

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.

Commits

  1. Change recovery_init_sync_method to PGC_SIGHUP.

  2. Provide recovery_init_sync_method=syncfs.