Tom Lane wrote: > Ron Mayer <[EMAIL PROTECTED]> writes: > > The most unambiguous behavior would be to not have > > commented out values in the config file at all. > > Yeah, Robert Treat suggested that upthread, and I think it's been pushed > by others too. > > The only argument I can see against it is that it'll take longer for the > system to process such a file; but do we really care about a few more > microseconds to respond to SIGHUP? > > This does not address the problem that changing PGC_POSTMASTER values in > the file won't do anything without a postmaster restart. Greg Stark's > suggestion of marking each PGC_POSTMASTER variable with a warning > comment in postgresql.conf seems reasonable to me, though.
We should issue a warning in the server logs if someone tries to modify a postmastger-only value on reload. Added to TODO: o Issue a warning if a change-on-restart-only postgresql.conf value is modified and the server config files are reloaded o Mark change-on-restart-only values in postgresql.conf -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq