Paul,
> Is there any reason we cannot ship with 3 .conf files? For each one,
> note the minimum system configuration required to support it.
>
> postgresql.conf.standard (current)
> postgresql.conf.medium (1Gb of RAM, IDE RAID 1 (7200RPM))
> postgresql.conf.performance (4Gb of RAM, SCSI RAID 10 (10000RPM))
Because too many of the conf parameters are dependant on *exactly* the
amount of RAM that you have. So there isn't even a general file we can
ship. Also medium/performance isn't adequate, we'd need:
.mixed.small_machine
.mixed.large_machine
.web.small_machine
.web.large_machine
.warehouse.large_machine
.... etc.
> I guess this gets back to auto-tuning scripts, and the difficulty of
> that, but it seems silly that every single person who installs
> postgresql has to independently learn that no, their shared_buffers
> need to be turned up. Assuming they don't give up early and assume
> that PgSQL performance sucks (as popular myth would have them believe
> to start with).
Your help with our project is welcome:
http://pgfoundry.org/projects/configurator/
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
