The proposal is to remove the comments from postgresql.conf (like Apache) so all entries will be active. The downside is that it will not be possible to determine which values were modified from their defaults.
One thing that truly annoys me about postgresql.conf is say I unhash an option and set it to something. Then I reload. Then I edit the conf and hash it out again, then I reload. Of course, the option still has my old value. This is really annoying and I've wasted lots of time trying to figure out what's going on.
Chris
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
