Re: Improving postgresql.conf

Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
[ PGP not available, raw data follows ]
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > Try yourself, I did the experiment changing the cpu_tuple_cost and
> > commenting out the cpu_tuple_cost, after sending the SIGHUP to
> > postmaster the value remain: 0.005 that is not the default value at
> > all.
>
> Ducking the added documentation discussion for a minute, I think we
> can agree that the commented-default concept is at the least confusing,
> at the most broken.
>
> > I understand your points below. However, the group has weighed in the
> > direction of clearly showing non-default values and not duplicating
> > documentation. We can change that, but you will need more folks
> > agreeing with your direction.
>
> How do we do determine this? Perhaps a reasoned discussion on hackers?
>
> I'll start, by putting forth the proposal that the default-comment
> behavior does more harm than good because it is confusing and broken,
> and should be scrapped in favor of a simple "what you see is what you get"
> behavior, just like every other configuration file.

OK, would other folks share their opinions on this issue?

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.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073