From: | Michael Brusser <michael(at)synchronicity(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Defaults for GUC variables (was Re: pg_ctl reports |
Date: | 2003-10-27 16:03:26 |
Message-ID: | DEEIJKLFNJGBEMBLBAHCKEIJDNAA.michael@synchronicity.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > Shouldn't it revert to the default value?
>
> No, not unless you think the postmaster should react to comments in the
> postgresql.conf file, which is rather against my idea of a comment.
>
> However, you're not the first to get burnt by this mis-assumption,
> so maybe we should do something about it.
>
> The low-tech solution to this would be to stop listing the default
> values as commented-out entries, but just make them ordinary uncommented
> entries. That way people who think "undoing my edit will revert the
> change" would be right.
>
> Or we could try to make it actually work the way you seem to be
> expecting. The only implementation I can think of is to reset GUC
> variables to defaults just before scanning the .conf file ...
------
I have to say we never had any problems or misconception with
how it currently works, but if this has to be changed I'd rather
vote for the low-tech solution.
Mike.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-10-27 16:05:58 | Re: Still a few flaws in configure's default CFLAGS selection |
Previous Message | Bruce Momjian | 2003-10-27 15:35:22 | Re: Call for port reports (Win32 Client) |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-10-27 16:44:02 | Re: pg_ctl reports succes when start fails |
Previous Message | Tom Lane | 2003-10-27 15:22:32 | Defaults for GUC variables (was Re: pg_ctl reports succes when start fails) |