Re: fdatasync performance problem with large number of DB files

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(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 <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: fdatasync performance problem with large number of DB files
Date: 2021-06-22 05:01:44
Message-ID: CA+hUKG+SG9jSW3ekwib0cSdC0yD-jReJ21X4bZAmqxoWTLTc2A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 18, 2021 at 1:11 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> Thomas, could you comment on this ?

Sorry, I missed that. It is initially a confusing proposal, but after
trying it out (that is: making recovery_init_sync_method PGC_SIGHUP
and testing a scenario where you want to make the next crash use it
that way and without the change), I agree. +1 from me.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2021-06-22 05:02:46 subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE
Previous Message Michael Paquier 2021-06-22 04:45:24 Re: fdatasync performance problem with large number of DB files