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).
IMHO the suggestion to just uncomment out all of the variables to begin with
would cut down on confusion a great deal and actually be easy to implement,
and as such is probably the way to go for now.
Robert Treat
On Wednesday 24 August 2005 15:43, Bruce Momjian wrote:
> OK, TODO updated:
>
> o %Allow commenting of variables in postgresql.conf to restore them
> to defaults
>
> Currently, if a variable is commented out, it keeps the
> previous uncommented value until a server restarted.
> Logically, a reload should set the same values as a
> server restart.
>
>
> ---------------------------------------------------------------------------
>
> Jim C. Nasby wrote:
> > On Wed, Aug 24, 2005 at 03:11:31PM -0400, Greg Stark wrote:
> > > In every other system I've seen, when you "reload" a config file the
> > > system goes through the exact same process (semantically at least) that
> > > it does when starting up. Ie, it start with a fresh slate of defaults
> > > and loads the config file which sets parameters and overrides those
> > > defaults.
> >
> > I think this is a good summary of the desired behavior, and that it
> > should be added to the TODO description.
> > --
> > Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
> > Pervasive Software http://pervasive.com 512-569-9461
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL