From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <pjmodos(at)seznam(dot)cz> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCHES] default resource limits |
Date: | 2005-12-25 00:46:30 |
Message-ID: | 4054.24.211.165.134.1135471590.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[moved to -hackers]
Petr Jelinek said:
> Andrew Dunstan wrote:
>>
>> Just because we can run with very little memory doesn't mean we have to.
What is the point of having lots of memory if you don't use it? We are
talking defaults here. initdb will still scale down on
>> resource-starved machines.
>>
>
> Why not just give user few configs tuned to different things like mysql
> does ? Or better, make it initdb option so it will try to set
> higher/lower limits depending on type of config.
>
And what settings will be tried by distros that automatically run initdb on
first startup?
I don't mind having an initdb option that tunes the settings tried, but that
doesn't remove the need to choose some defaults.
I'm not sure that I think mysql's setup is a good example to follow.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-12-25 00:56:50 | Re: Fixing row comparison semantics |
Previous Message | Kevin Brown | 2005-12-25 00:14:19 | Re: Unsplitting btree index leaf pages |