| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bernd Helmle <mailings(at)oopsware(dot)de>, "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Change default of checkpoint_completion_target |
| Date: | 2020-12-10 17:16:02 |
| Message-ID: | 20201210171602.GP16415@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
* Laurenz Albe (laurenz(dot)albe(at)cybertec(dot)at) wrote:
> On Tue, 2020-12-08 at 17:29 +0000, Bossart, Nathan wrote:
> > +1 to setting checkpoint_completion_target to 0.9 by default.
>
> +1 for changing the default or getting rid of it, as Tom suggested.
Attached is a patch to change it from a GUC to a compile-time #define
which is set to 0.9, with accompanying documentation updates.
> While we are at it, could we change the default of "log_lock_waits" to "on"?
While I agree that it'd be good to change quite a few of the log_X items
to be 'on' by default, I'm not planning to work on this.
Thanks,
Stephen
| Attachment | Content-Type | Size |
|---|---|---|
| cct_def_v2.patch | text/x-diff | 13.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-12-10 17:21:26 | Re: Change default of checkpoint_completion_target |
| Previous Message | Konstantin Knizhnik | 2020-12-10 16:44:03 | Re: Hybrid Hash/Nested Loop joins and caching results from subplans |