From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | josh(at)agliodbs(dot)com |
Cc: | Justin Clift <justin(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rod Taylor <rbt(at)rbt(dot)ca>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal to Re-Order Postgresql.Conf, part II |
Date: | 2003-06-10 17:46:36 |
Message-ID: | 3EE6197C.6010504@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Okay, separate documentation might work ;-)
Jan
Josh Berkus wrote:
> Jan,
>
>> No, not documenting it IS a good move.
>
> I couldn't disagree more. Undocumented options? Who are we, Microsoft?
>
>> If there's a button people will
>> press it, if there's a switch people will turn it on and if there's a
>> slot people will stick in whatever they have ... believe it or not, I
>> have found a Xmas cookie in the floppy drive of a consultant's notebook
> <snip>
>
> These kinds of people don't read the documentation in the first place, so
> we're in no danger from them.
>
> I can definitely see an argument that the "developer" switches should be
> documented on a different page of the docs from "Run-Time Configuration".
> But the idea of having GUCs that aren't documented at all, anywhere, is a
> very anti-Open Source idea.
>
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-06-10 17:47:15 | Re: Character encoding |
Previous Message | Peter Eisentraut | 2003-06-10 17:45:50 | Re: Groups and roles |