X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.192]) by svr1.postgresql.org (Postfix) with ESMTP id 9EF68CD2A2 for ; Sun, 20 Jul 2003 19:20:40 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr4.postgresql.org [64.117.224.192]) (amavisd-new, port 10024) with ESMTP id 37959-02 for ; Sun, 20 Jul 2003 19:21:17 +0000 (GMT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id B8A4BCD2A1 for ; Sun, 20 Jul 2003 16:20:38 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h6KJL6a10673; Sun, 20 Jul 2003 15:21:06 -0400 (EDT) From: Bruce Momjian Message-Id: <200307201921.h6KJL6a10673@candle.pha.pa.us> Subject: Re: Moving postgresql.conf tunables into 2003... In-Reply-To: To: Michael Pohl Date: Sun, 20 Jul 2003 15:21:06 -0400 (EDT) Cc: pgsql-performance@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/311 X-Sequence-Number: 2604 Michael Pohl wrote: > On Sun, 6 Jul 2003, Matthew Nuzum wrote: > > > At the very least, if there is good documentation for these parameters, > > maybe the conf file should provide a link to this info. > > I believe that is what Josh is proposing: > > http://archives.postgresql.org/pgsql-performance/2003-07/msg00102.php > > > [Apache httpd] uses a three phase (if not more) documentation level. > > The .conf file contains detailed instructions in an easy to read and > > not-to-jargon-ish structure. The docs provide detailed tutorials and > > papers that expand on configuration params in an easy to read format. > > Both of these refer to the thorough reference manual that breaks each > > possible option down into it's nitty gritty details so that a user can > > get more information if they so desire. > > I agree that Apache's approach is primo. Often the .conf comments are > enough to jog my memory about a directive I haven't used for a while. Or > the comments are enough to let me know I don't need a directive, or that I > need to go to the manual and read more. I appreciate that. Isn't that what we have now --- isn't postgresql.conf clear enough to jog people's memory. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073