Re: fdatasync performance problem with large number of DB files

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Paul Guo <guopa(at)vmware(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Brown <michael(dot)brown(at)discourse(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: fdatasync performance problem with large number of DB files
Date: 2021-03-19 11:01:34
Message-ID: 20210319110134.GJ11765@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2021-03-19 11:48:22 Re: Asynchronous Append on postgres_fdw nodes.
Previous Message wangsh.fnst@fujitsu.com 2021-03-19 10:11:46 RE: invalid data in file backup_label problem on windows