Nick,
> I agree... but are we the folks that the conf file needs to be made more
> intuitive for?
>
> If the intent is to make it easier for experienced folks like ourselves who
> are working with large or unusual databases to deal with PostgreSQL, then
> certainly the resource usage and tuning settings should go to the top.
> We'll set the other params once & never touch them again.
>
> On the other hand, I suspect that the majority of postgresql users play
> with the other params a bit during install to get their systems working and
> never touch the resource usage or tuning params ever. (And this is as it
> should be, given that the defaults are reasonable for most systems.)
This is a good argument. Though if you pursue it, surely you're advocating a
GUI tool for PostgreSQL.conf, not that that's a bad idea ...
How do other people feel about this? What options in PostgreSQL.conf do you
tweak most frequently?
--
Josh Berkus
Aglio Database Solutions
San Francisco