Horton

Re: fdatasync performance problem with large number of DB files

Justin Pryzby <pryzby@telsasoft.com>

View thread View on postgr.es
From: Justin Pryzby <pryzby@telsasoft.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Bruce Momjian <bruce@momjian.us>, Paul Guo <guopa@vmware.com>, Tom Lane <tgl@sss.pgh.pa.us>, Michael Brown <michael.brown@discourse.org>, pgsql-hackers@postgresql.org
Date: 2021-03-19T11:01:34Z
Lists: pgsql-hackers 
On Fri, Mar 19, 2021 at 06:28:46PM +1300, Thomas Munro wrote:
> +++ b/doc/src/sgml/config.sgml

> +        <productname>PostgreSQL</productname> will recursively open and fsync
> +        all files in the data directory before crash recovery begins.  This

Maybe it should say "data, tablespace, and WAL directories", or just "critical
directories".

> +	{
> +		{"recovery_init_sync_method", PGC_POSTMASTER, ERROR_HANDLING_OPTIONS,
> +			gettext_noop("Sets the method for synchronizing the data directory before crash recovery."),
> +		},

"and tablespaces and WAL"

-- 
Justin

Commits

  1. Change recovery_init_sync_method to PGC_SIGHUP.

  2. Provide recovery_init_sync_method=syncfs.