> Hello, > > As I have been laboring over the documentation of the postgresql.conf > file for 8.1dev it seems that it may be useful to rip out most of the > options in this file? > > Considering many of the options can already be altered using SET why > not make it the default for many of them? > > Sincerely, > > Joshua D. Drake >
Well, if you want PostgreSQL to act a specific way, then you are going to have to set up the defaults somehow, right? Which is cleaner? Using a configuration file which is going to be there anyway, or trying to rig-up some sort of autostart.sql mechanism to put PostgreSQL into its desired state? I periodically get into arguments on hackers because I want *more* options available in postgresql.conf My dream is to start postgres like: /opt/postgres/bin/postmaster --config-file=/opt/postgres/bases/tiger.conf or /opt/postgres/bin/postmaster --config-file=/opt/postgres/bases/zipcode.conf I also want an include directve that allows production or debugging settings to be easily used. ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
