| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Sebastian Hennebrueder <usenet(at)laliluna(dot)de> |
| Subject: | Re: Feature Request --- was: PostgreSQL Performance Tuning |
| Date: | 2007-05-06 05:38:10 |
| Message-ID: | A319E17E-3214-4A05-8733-2913D2495B43@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On May 4, 2007, at 12:11 PM, Josh Berkus wrote:
> Sebastian,
>> Before inventing a hyper tool, we might consider to provide 3-5
>> example
>> szenarios for common hardware configurations. This consumes less time
>> and be discussed and defined in a couple of days. This is of
>> course not
>> the correct option for a brandnew 20 spindle Sata 10.000 Raid 10
>> system
>> but these are probably not the target for default configurations.
>
> That's been suggested a number of times, but some GUCs are really
> tied to the
> *exact* amount of RAM you have available. So I've never seen how
> "example
> configurations" could help.
Uh... what GUCs are that exacting on the amount of memory? For a
decent, base-line configuration, that is.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kostyrka | 2007-05-06 07:06:02 | Re: Feature Request --- was: PostgreSQL Performance Tuning |
| Previous Message | Scott Ribe | 2007-05-06 00:28:40 | Re: Casting to varchar |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kostyrka | 2007-05-06 07:06:02 | Re: Feature Request --- was: PostgreSQL Performance Tuning |
| Previous Message | Yudhvir Singh Sidhu | 2007-05-06 04:52:56 | Re: How to Find Cause of Long Vacuum Times - NOOB Question |