Subject: Re: Change default of checkpoint_completion_target
To: Stephen Frost <sfrost@snowman.net>,
 Alvaro Herrera <alvherre@alvh.no-ip.org>
References: <20201210171602.GP16415@tamriel.snowman.net>
 <20201210172126.GA25979@alvherre.pgsql>
 <20201210172255.GQ16415@tamriel.snowman.net>
 <20210113221038.GG27507@tamriel.snowman.net>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
 "Bossart, Nathan" <bossartn@amazon.com>,
 Michael Paquier <michael@paquier.xyz>, Bernd Helmle <mailings@oopsware.de>,
 "tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Organization: EnterpriseDB
Message-ID: <ba8bb5e9-8c43-11b6-eb99-ae794cd37665@enterprisedb.com>
Date: Tue, 19 Jan 2021 09:21:15 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0)
 Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20210113221038.GG27507@tamriel.snowman.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2021-01-13 23:10, Stephen Frost wrote:
>> Yes, I agree, and am involved in that thread as well- currently waiting
>> feedback from others about the proposed approach.
> I've tried to push that forward.  I'm happy to update this patch once
> we've got agreement to move forward on that, to wit, adding to an
> 'obsolete' section in the documentation information about this
> particular GUC and how it's been removed due to not being sensible or
> necessary to continue to have.

Some discussion a few days ago was arguing that it was still necessary 
in some cases as a way to counteract the possible lack of tuning in the 
kernel flushing behavior.  I think in light of that we should go with 
your first patch that just changes the default, possibly with the 
documentation updated a bit.