| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, 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-06-18 09:18:59 |
| Message-ID: | 2589e842-41be-5d83-4616-216acf0a59da@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/06/04 23:39, Justin Pryzby wrote:
> You said switching to SIGHUP "would have zero effect"; but, actually it allows
> an admin who's DB took a long time in recovery/startup to change the parameter
> without shutting down the service. This mitigates the downtime if it crashes
> again. I think that's at least 50% of how this feature might end up being
> used.
Yes, it would have an effect when the server is automatically restarted
after crash when restart_after_crash is enabled. At least for me +1 to
your proposed change.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2021-06-18 10:20:22 | Re: disfavoring unparameterized nested loops |
| Previous Message | osumi.takamichi@fujitsu.com | 2021-06-18 08:55:17 | RE: locking [user] catalog tables vs 2pc vs logical rep |