| 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 21:37:25 |
| Message-ID: | 603c8f070812031337q16a6ff42p48a0eb189cae12bd@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I can see an argument about constraint_exclusion but
> default_statistics_target I don't.
Why not? I don't want to accept a big increase in ANALYZE times (or
planning times, though I'm really not seeing that at this point)
without some benefit.
>> It seems unlikely that you would want 256 MB of checkpoint segments on
>> a database that is only 100 MB (or even 500 MB). But you might very
>> well want that on a database that is 1 TB.
>
> 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?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-12-03 21:41:56 | Re: Simple postgresql.conf wizard |
| Previous Message | Robert Haas | 2008-12-03 21:29:15 | Re: Simple postgresql.conf wizard |