pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Bossart, Nathan <bossartn@amazon.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: David Steele <david@pgmasters.net>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
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>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Change default of checkpoint_completion_target
Date: Tue, 23 Mar 2021 14:30:33 -0400
Message-ID: <20210323183033.GI579@momjian.us> (raw)
In-Reply-To: <E4F12190-A523-447B-BC35-E868CA5796F4@amazon.com>
References: <20210113221038.GG27507@tamriel.snowman.net>
	<ba8bb5e9-8c43-11b6-eb99-ae794cd37665@enterprisedb.com>
	<20210119191450.GO27507@tamriel.snowman.net>
	<519044.1611084646@sss.pgh.pa.us>
	<20210119194748.GP27507@tamriel.snowman.net>
	<c564d4d9-27cc-0a7b-9d98-adf65fe9e825@pgmasters.net>
	<20210322171059.GB20766@tamriel.snowman.net>
	<YFl9MuiWf6iBbj1W@paquier.xyz>
	<20210323162446.GL20766@tamriel.snowman.net>
	<E4F12190-A523-447B-BC35-E868CA5796F4@amazon.com>

On Tue, Mar 23, 2021 at 06:24:07PM +0000, Bossart, Nathan wrote:
> LGTM.  I just have a few small wording suggestions.
> 
> +        completion overhead.  Reducing this parameter is not recommended as that
> +        causes the I/O from the checkpoint to have to complete faster, resulting
> +        in a higher I/O rate, while then having a period of less I/O between the
> +        completion of the checkpoint and the start of the next scheduled
> +        checkpoint.  This parameter can only be set in the
> 
> Reducing this parameter is not recommended because it forces the
> checkpoint to complete faster.  This results in a higher rate of I/O
> during the checkpoint followed by a period of less I/O between
> checkpoint completion and the next scheduled checkpoint.

FYI, I am very happy this issue is being addressed for PG 14.  :-)

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  If only the physical world exists, free will is an illusion.






view thread (30+ messages)  latest in thread

Message-ID: <20210323183033.GI579@momjian.us>
Permalink:  ../20210323183033.GI579@momjian.us/
Also on:    postgresql.org/message-id/20210323183033.GI579@momjian.us

 · 

reply

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: bruce@momjian.us, bossartn@amazon.com, sfrost@snowman.net, michael@paquier.xyz, david@pgmasters.net, peter.eisentraut@enterprisedb.com, alvherre@alvh.no-ip.org, laurenz.albe@cybertec.at, mailings@oopsware.de, tsunakawa.takay@fujitsu.com, tgl@sss.pgh.pa.us
  Subject: Re: Change default of checkpoint_completion_target
  In-Reply-To: <20210323183033.GI579@momjian.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