From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, jd(at)commandprompt(dot)com, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Simple postgresql.conf wizard |
Date: | 2008-12-04 07:33:07 |
Message-ID: | 493787B3.10604@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Gregory Stark escribió:
>> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>
>>> I don't think at any time I have said to my self, I am going to set this
>>> parameter low so I don't fill up my disk. If I am saying that to myself
>>> I have either greatly underestimated the hardware for the task. Consider
>>> that we are quarreling over what amounts to a nominal amount of hard
>>> drive space, 1000 checkpoint_segments = 1.6G of space. My phone has more
>>> capacity than that.
>> Well my phone has 16G of RAM, why not 10000 ?
>
> I don't think the disk space used is the only consideration here. You
> also have to keep recovery time in mind. If you set it to 1000,
> recovery would take way too long.
Presumably if you set checkpoint_segments to a high value, you'd use
checkpoint_timeout to limit recovery time.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2008-12-04 07:35:27 | Re: In-place upgrade: catalog side |
Previous Message | Zdenek Kotala | 2008-12-04 07:21:04 | Re: In-place upgrade: catalog side |