| From: | Sebastian Hennebrueder <usenet(at)laliluna(dot)de> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Feature Request --- was: PostgreSQL Performance Tuning |
| Date: | 2007-05-04 17:22:31 |
| Message-ID: | 463B6BD7.7010308@laliluna.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
Josh Berkus schrieb:
> 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.
>
>
I would define the szenario as
256 MB freely available for PostgresQL
=> setting x can be of size ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2007-05-04 17:23:38 | Re: varchar as primary key |
| Previous Message | Mike Frysinger | 2007-05-04 17:18:09 | Re: cant get pg_dump/pg_restore to behave |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2007-05-05 01:07:53 | Re: Feature Request --- was: PostgreSQL Performance Tuning |
| Previous Message | Josh Berkus | 2007-05-04 17:11:42 | Re: Feature Request --- was: PostgreSQL Performance Tuning |