| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: TODO questions |
| Date: | 2005-08-24 14:47:19 |
| Message-ID: | 25846.1124894839@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Jim C. Nasby wrote:
>> o Allow commenting of variables in postgresql.conf to restore them
>> to defaults
>>
>> This doesn't work already?
> The idea here is the when you comment something out, it should restore
> its default. Right now it keeps the previously uncommented out value,
> which confuses people.
But the contrary position is that a comment is a comment, not something
that should act to change the state of the postmaster.
It's probably worth pointing out that there's not consensus about all
of the TODO items, particularly not the ones Bruce has marked with
question marks.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2005-08-24 15:41:20 | Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited) |
| Previous Message | Tom Lane | 2005-08-24 14:41:42 | FYI: 8.1beta1 today |