Adrian 'Dagurashibanipal' von Bidder writes: > - postgres should auto-tune itself - the *cost could perhaps be > adjusted after some statistics have been collected, and there should be > some sensible way to determine an optimal setting for the famous > shared_buffers (and the default should be something that gets reasonable > performance on common cases)
Over the last couple of years PostgreSQL has transformed from hardly configurable to fully configurable. Currently we're in a mode where we add new configuration parameters whenever there's a degree of uncertainty. Sooner rather than later we need to shift to the next phase, which is as you say autoconfiguration, because ease of administration is one of the great advantages of PostgreSQL. -- Peter Eisentraut [EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
