Re: remove checkpoint_warning - Mailing list pgsql-hackers

From Robert Haas
Subject Re: remove checkpoint_warning
Date
Msg-id CA+TgmoYWeM=cGLmKGOb-G_WyMbLLT-_e802C1d5CcULbJvpSYg@mail.gmail.com
Whole thread Raw
In response to Re: remove checkpoint_warning  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Tue, Jul 12, 2016 at 3:19 AM, Magnus Hagander <magnus@hagander.net> wrote:
> +1, this is a useful warning.

+1.

I'd like to see more people turn log_checkpoints=on, and I often ask
customers to do that when they're having systemic performance
problems.  But this warning regularly alerts me to cases where I've
failed to configure max_wal_size to an adequately large value.  It's
true that the new values are less conservative than the old ones, but
they're still pretty conservative.  Anybody who still thinks that 1GB
is a lot of disk space might be due for a hardware upgrade.  I
regularly need to increase that value substantially on my *laptop*.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgbench - allow to store select results into variables
Next
From: Robert Haas
Date:
Subject: Re: pgbench - allow to store select results into variables