Re: TODO questions - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: TODO questions
Date
Msg-id 430C99E9.4000701@commandprompt.com
Whole thread Raw
In response to Re: TODO questions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TODO questions  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
Re: TODO questions  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-hackers
>>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.
>  
>
Not in any conf I have ever seen. If I comment out a parameter
I expect that the parameter will either be disabled or set to the
default depending on the parameter.

#fsync = false

Should mean:

fsync = false

--

fsync = true

Should mean:

fsync = true

--

#fsync = true:

Should mean:

fsync = false

If false is the default value.

--

Sincerely,

Joshua D. Drake

>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
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>  
>



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)
Next
From: "Kevin McArthur"
Date:
Subject: FreeBSD ICU was Win32 unicode vs ICU