| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remove checkpoint_warning |
| Date: | 2016-07-13 20:03:49 |
| Message-ID: | CA+TgmoYWeM=cGLmKGOb-G_WyMbLLT-_e802C1d5CcULbJvpSYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 12, 2016 at 3:19 AM, Magnus Hagander <magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-07-13 20:07:16 | Re: pgbench - allow to store select results into variables |
| Previous Message | Tom Lane | 2016-07-13 20:02:23 | Re: pgbench - allow to store select results into variables |