-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Feb 2008 23:02:34 -0500 Aidan Van Dyk <[EMAIL PROTECTED]> wrote:
> * Joshua D. Drake <[EMAIL PROTECTED]> [080220 21:15]: > > > The one thing this does is make the postgresql.conf basically a > > placeholder. It is not definitive anymore, in the sense that > > settings will be overwritten on restart. That really isn't that > > uncommon anyway in other applications. > > Man, I'ld screem *bloody murder* if the config file we just finished, > after spending days (or weeks) of careful analisys and implementation > discussion was "overwritten" by postmaster "automatically" on server > startup... And I of course would respond, read the docs :P > > But part of that might just be user education... I personally just > can't imagine that education could be enough to let *all* users know > that as of version S, postgresql.conf is blatantly ignored, no, more > exactly *purposely overwritten* with the "old" settings... We could also make it optional. Sincerely, Joshua D. Drake - -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHvPkJATb/zqfZUUQRAqNlAJ972s1p0RvfWabRXOQKkzJvACkEYQCfXrsc IZ18stRvr6NONj0T3wUBpXE= =nWtF -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
