Re: [HACKERS] Status of TODO: postgresql.conf: reset to default when
On Sun, Mar 05, 2006 at 01:23:10PM -0500, Bruce Momjian wrote: 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. I take that to apply to the configuration re-read at SIGHUP? Right, and it is something we have needed to fix for a while. I'm working on this one. Joachim -- Joachim Wieland [EMAIL PROTECTED] C/ Usandizaga 12 1°B ICQ: 37225940 20002 Donostia / San Sebastian (Spain) GPG key available ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[HACKERS] Status of TODO: postgresql.conf: reset to default when commented
Hi, What's the status of the TODO item 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. I take that to apply to the configuration re-read at SIGHUP? Markus Bertheau ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Status of TODO: postgresql.conf: reset to default when
Markus Bertheau wrote: Hi, What's the status of the TODO item 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. I take that to apply to the configuration re-read at SIGHUP? Right, and it is something we have needed to fix for a while. -- Bruce Momjian http://candle.pha.pa.us SRA OSS, Inc. http://www.sraoss.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 6: explain analyze is your friend
