X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 0F4ABB42002 for ; Mon, 7 Jul 2003 03:45:36 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 62352-09 for ; Mon, 7 Jul 2003 00:45:22 -0300 (ADT) Received: from ethereal-realms.org (thebe.ethereal-realms.org [142.179.222.205]) by svr1.postgresql.org (Postfix) with ESMTP id E526AB42001 for ; Mon, 7 Jul 2003 00:45:21 -0300 (ADT) Received: from ethereal-realms.org (ip14.ethereal-realms.COM [192.168.1.14]) by ethereal-realms.org (8.12.6/8.12.6) with ESMTP id h673gnPu024255; Sun, 6 Jul 2003 21:42:49 -0600 (MDT) Message-ID: <3F08EC37.6020303@ethereal-realms.org> Date: Sun, 06 Jul 2003 21:42:47 -0600 From: Martin Foster Organization: Ethereal Realms User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Pohl , PostgreSQL Performance Subject: Re: Moving postgresql.conf tunables into 2003... References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/121 X-Sequence-Number: 2414 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. > > michael > One thing that may also help, is to include more sample .conf files. For example, you could include settings that would be commonly seen for decicated databases with generic specs and another with less resources and not dedicated for use with Postgres. This would allow users to see how certain setting changes will work. The default .conf is great if you want to setup a small test bed, but for a real life example chances are it won't exactly be what your looking for. Martin Foster Creator/Designer Ethereal Realms martin@ethereal-realms.org