public inbox for [email protected]
help / color / mirror / Atom feedFrom: elein <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Documentation of server configuration
Date: Sat, 13 Nov 2004 17:05:11 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Is it possible to have an alphabetical hyperlink index to the sections?
I really like that it is in the same order as those in the
file and the like parameters are grouped.
But the table is too big and needs an index for faster access...
no wait that was the database...no wait...
elein
On Sat, Nov 13, 2004 at 09:20:51PM +0100, Peter Eisentraut wrote:
> I've just spent a day working through the current set of server
> configuration parameters, and I think that the documentation at
> <http://developer.postgresql.org/docs/postgres/runtime-config.html; has
> reached its peak of unusability. I haven't been able to find a single
> parameter all day except by using a text search over the file.
>
> A couple of obvious faults:
>
> - There are too many sections.
>
> - The sections don't have any obvious order.
>
> - The subsections don't have any obvious order.
>
> - The lists of individual parameters inside the sections don't have any
> order.
>
> - If a parameter has a list of possible values, the values are not
> listed in a consistent order.
>
> I have made an attempt and reformatted the whole section into one big
> alphabetical list, and while that has obvious drawbacks, I feel that
> it's already much more usable than what we have now.
>
> Other ideas?
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
view thread (22+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Documentation of server configuration
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox