Re: Simple postgresql.conf wizard

From: "Robert Haas" <robertmhaas(at)gmail(dot)com>
To: jd(at)commandprompt(dot)com
Cc: "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-03 22:33:56
Message-ID: 603c8f070812031433p50c03a9w5b51e14429538968@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 3, 2008 at 4:41 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> If you are concerned about the analyze time between 10, 50 and 150, I
> would suggest that you are concerned about the wrong things. Remember

I can't rule that out. What things do you think I should be concerned
about? ISTM that default_statistics_target trades off ANALYZE time
and query planning time vs. the possibility of better plans. If the
former considerations are not an issue for dst = 50, then maybe we
should emit 50 by default. But the limited evidence that has been
published in this forum thus far doesn't support that contention.

>> > It also seems unlikely that you would hit 256MB of checkpoint segments
>> > on a 100MB database before checkpoint_timeout and if you did, you
>> > certainly did need them.
>>
>> So why do we have this parameter at all?
>
> Excellent question, for a different thread :)

I think the rhetorical answer is "so that we don't fill up the disk",
which gets us back to database size.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-12-03 22:38:53 Re: Visibility map, partial vacuums
Previous Message Gregory Stark 2008-12-03 22:01:24 Re: Simple postgresql.conf wizard