-----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. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200406151936 -----BEGIN PGP SIGNATURE----- iD8DBQFAz4iBvJuQZxSWSsgRAkO8AKD7t4qdWbeqs7aAuw5ZsQOsKUwGQACfb0/Y x+vvo6KZ2NgZ9i+4BjIX9yg= =13P0 -----END PGP SIGNATURE-----
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
