> -----Original Message----- > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 24, 2005 3:40 PM > To: Robert Treat > Cc: pgsql-hackers@postgresql.org; Jim Nasby; Greg Stark; Tom Lane > Subject: Re: [HACKERS] TODO questions > > > Robert Treat wrote: > > I've always been of the impression that this idea just wont > work. For > > example, if I set shared_buffers to some number, start my > database, then > > comment the line out and "reload" my conf file, it just > isnt going to reset > > to the default. (Or at least to make it do so requires a > *lot* more work than > > just modifing the guc / conf file mechanisms). > > True, but you can't modify shared_buffers anyway unless you > restart, so > people should realize that.
Which is why I think it would be best to get as close as we can to the configuration that you'd get during a restart and warn about everything else. So, for example, if you're runing with a non-default shared_buffers and you comment shared_buffers out and do a reload, you should get a warning that shared_buffers has changed from xxx -> yyy but that change won't take effect until the server is restarted. That way there's absolutely no confusion. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
