| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, 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-05-26 00:13:59 |
| Message-ID: | 20210526001359.GE3676@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 20, 2021 at 12:16:27PM +1300, Thomas Munro wrote:
> > > + {
> > > + {"recovery_init_sync_method", PGC_POSTMASTER, ERROR_HANDLING_OPTIONS,
> > > + gettext_noop("Sets the method for synchronizing the data directory before crash recovery."),
> > > + },
Is there any reason why this can't be PGC_SIGHUP ?
(Same as restart_after_crash, remove_temp_files_after_crash)
As neat as it'd be, I am not expecting the recovery process to reload the
configuration and finish fast if I send it HUP.
While I'm looking, it's not clear why this needs to be PGC_POSTMASTER.
data_sync_retry - but see b3a156858
This one isn't documented as requiring a restart:
max_logical_replication_workers.
ignore_invalid_pages could probably be SIGHUP, but it's intended to be used as
a commandline option, not in a config file.
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-05-26 00:36:52 | Re: automatic analyze: readahead - add "IO read time" log message |
| Previous Message | Stephen Frost | 2021-05-26 00:03:14 | Re: storing an explicit nonce |