Tom Lane wrote: > Andreas Pflug <[EMAIL PROTECTED]> writes: > > How about vars overridden on the postmaster command line? Similar issue, > > I believe. Naively, I'd assume that my last instruction (in this case: > > changing postgresql.conf and SIGHUP) would determine processing, which > > is obviously wrong if I read the docs correctly. > > That was another point I was about to make, which is that there are lots > of other reasons why the active value of some config variable might not > be what postgresql.conf says. We are *not* ripping out the entire GUC > facility just because some people haven't bothered to read the > documentation about it ;-). > > Maybe the real problem here is that people think that postgresql.conf > is the place to find out about current settings, and they just need to > be re-educated to look at pg_settings or SHOW ALL instead.
True. A postmaster arg, per-user or per-db setting, PGOPTIONS value, or .psqlrc overrides postgresql.conf. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (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: 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
