| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Brown <michael(dot)brown(at)discourse(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fdatasync performance problem with large number of DB files |
| Date: | 2021-03-16 08:10:28 |
| Message-ID: | 6d4a78fa-f18a-e40c-8e39-a069f9d9bca8@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/03/15 8:33, Thomas Munro wrote:
> On Mon, Mar 15, 2021 at 11:52 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>> Time being of the essence, here is the patch I posted last year, this
>> time with a GUC and some docs. You can set sync_after_crash to
>> "fsync" (default) or "syncfs" if you have it.
>
> Cfbot told me to add HAVE_SYNCFS to Solution.pm, and I fixed a couple of typos.
Thanks for the patch!
+ When set to <literal>fsync</literal>, which is the default,
+ <productname>PostgreSQL</productname> will recursively open and fsync
+ all files in the data directory before crash recovery begins.
Isn't this a bit misleading? This may cause users to misunderstand that
such fsync can happen only in the case of crash recovery.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gkokolatos | 2021-03-16 08:11:57 | Re: Allow batched insert during cross-partition updates |
| Previous Message | Kyotaro Horiguchi | 2021-03-16 07:51:41 | comment fix in postmaster.c |