On Tue, Aug 19, 2008 at 09:39:39PM +0300, Peter Eisentraut wrote: > On Tuesday 19 August 2008 19:12:16 Tom Lane wrote: > > Well, why not just make a one-eighty and say that the default > > postgresql.conf is *empty* (except for whatever initdb puts into it)? > > Well, my original implementation of GUC had an empty default configuration > file, which was later craptaculated to its current form based on seemingly > popular demand. I am very happy to work back toward the empty state, and > there appears to be growing support for that.
I like the almost empty file idea. I often use the include facility to setup postgresql.conf files that look roughly like this: #include postgresql_site_policy.conf #include postgresql_<host_class>.conf listen_port=9999 where the included files set things like the overall sites logging preferences and buffer_cache and workmen based on installed memory and disk system (ex: postgresql_32GB.conf) etc. -dg -- David Gould [EMAIL PROTECTED] 510 536 1443 510 282 0869 If simplicity worked, the world would be overrun with insects. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
