From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TODO questions |
Date: | 2005-08-24 19:43:26 |
Message-ID: | 200508241943.j7OJhQ403878@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)pervasive(dot)com
> Pervasive Software http://pervasive.com 512-569-9461
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-08-24 20:09:09 | Re: [HACKERS] Proposed patch to getaddrinfo.c to support |
Previous Message | Jim C. Nasby | 2005-08-24 19:35:08 | Re: TODO questions |