Carlos,
about your feature proposal: as I learned, nearly all Perfomance.Configuration can be done by editing the .INI file and making the Postmaster re-read it.
So, WHY at all should those parameters be guessed at the installation of the database? Would'nt it be a saver point of time to have some postgresql-tune
utilitiy, which gets run after the installation, maybe every once in a while. That tool can check vital information like "Databasesize to memory relation"; and suggest a new postgresql.ini.
That tool needs NO INTEGRATION whatsoever - it can be developed, deployed totally independend and later only be bundled.
Does my suggestion make more sense now? Or is it still too unrealistic to
make it work properly/safely?
And as this tool can be tested seperately, does not need a new initdb every time ... it can be developed more easily.
Maybe there is even a pointy flashy version possible (perhaps even for money :) which gives nice graphics and "optimized", like those Windows Optimizers. :) I am sure, some DBAs in BIGCOMPs would be thrilled :)
May that be a possible way?
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
fx 01212-5-13695179
-
Python: the only language with more web frameworks than keywords.
