From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bossart, Nathan <bossartn@amazon.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Bernd Helmle <mailings@oopsware.de>
Cc: tsunakawa.takay@fujitsu.com <tsunakawa.takay@fujitsu.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Change default of checkpoint_completion_target
Date: Tue, 08 Dec 2020 12:41:35 -0500
Message-ID: <3258483.1607449295@sss.pgh.pa.us> (raw)
In-Reply-To: <7CFCC359-5786-40DB-90A8-BDB0F08F2ABC@amazon.com>
References: <20201207175329.GM16415@tamriel.snowman.net>
<5285eb02-3340-7728-9f62-1a4365eda850@enterprisedb.com>
<20201207191742.GN16415@tamriel.snowman.net>
<7CFCC359-5786-40DB-90A8-BDB0F08F2ABC@amazon.com>
"Bossart, Nathan" <bossartn@amazon.com> writes:
> On 12/7/20, 9:53 AM, "Stephen Frost" <sfrost@snowman.net> wrote:
>> Concretely, attached is a patch which changes the default and updates
>> the documentation accordingly.
> +1 to setting checkpoint_completion_target to 0.9 by default.
FWIW, I kind of like the idea of getting rid of it completely.
Is there really ever a good reason to set it to something different
than that? If not, well, we have too many GUCs already, and each
of them carries nonzero performance, documentation, and maintenance
overhead.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, bossartn@amazon.com, sfrost@snowman.net, peter.eisentraut@enterprisedb.com, michael@paquier.xyz, alvherre@alvh.no-ip.org, laurenz.albe@cybertec.at, mailings@oopsware.de, tsunakawa.takay@fujitsu.com
Subject: Re: Change default of checkpoint_completion_target
In-Reply-To: <3258483.1607449295@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox