| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Venkata Balaji N <nag1010(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Redesigning checkpoint_segments |
| Date: | 2015-02-03 15:00:20 |
| Message-ID: | 2046901824.936101.1422975620240.JavaMail.yahoo@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
> On 02/02/2015 04:21 PM, Andres Freund wrote:
>> On 2015-02-02 08:36:41 -0500, Robert Haas wrote:
>>> Also, I'd like to propose that we set the default value of
>>> max_checkpoint_segments/checkpoint_wal_size to something at
>>> least an order of magnitude larger than the current default
>>> setting.
>>
>> +1
>
> I don't agree with that principle. I wouldn't mind increasing it
> a little bit, but not by an order of magnitude.
Especially without either confirming that this effect is no longer
present, or having an explanation for it:
http://www.postgresql.org/message-id/4A44E58C0200002500027FCF@gw.
wicourts.gov
Note that Greg Smith found the same effect on a machine without any
write caching, which shoots down my theory, at least on his
machine:
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | José Luis Tallón | 2015-02-03 15:01:05 | Re: Fwd: [GENERAL] 4B row limit for CLOB tables |
| Previous Message | David Fetter | 2015-02-03 15:00:14 | Re: Release note bloat is getting out of hand |