X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4A7093A478B for ; Mon, 15 Nov 2004 18:18:16 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 96717-07 for ; Mon, 15 Nov 2004 18:17:57 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id AC9CB3A47DC for ; Mon, 15 Nov 2004 18:17:57 +0000 (GMT) Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6664228; Mon, 15 Nov 2004 10:19:25 -0800 From: Josh Berkus Organization: Aglio Database Solutions To: Neil Conway Subject: Re: Documentation of server configuration Date: Mon, 15 Nov 2004 10:16:53 -0800 User-Agent: KMail/1.6.2 Cc: Simon Riggs , Peter Eisentraut , pgsql-docs@postgresql.org References: <200411132120.51294.peter_e@gmx.net> <1100449519.2950.1123.camel@localhost.localdomain> <1100493852.23420.33.camel@localhost.localdomain> In-Reply-To: <1100493852.23420.33.camel@localhost.localdomain> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200411151016.53648.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/34 X-Sequence-Number: 2669 Neil, > I agree that this section is frequently accessed. Given that, I think it > is somewhat difficult to find -- we've all memorized that it is in the > "Server Run-time Environment" chapter, but I don't think that's the > first place most people would look. What do people think about > separating the configuration section out to be a new top-level chapter? I'd be up for that. The trick will be getting it done before 8.0 ... although if we're going into another beta, maybe time isn't precious yet. Actually, what I'd see is: 1) a section explaining the most frequently modified options, and links; 2) a section grouping options by general purpose (like our current categories), with links; 3) a dictionary of config options, which personally I would prefer to be one per page like the SQL commands. If we were to do the above, then re-ordering the "dictionary" to pure alphabetical would make perfect sense. -- Josh Berkus Aglio Database Solutions San Francisco