X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id EC35430E798 for ; Tue, 10 Jun 2003 19:05:29 +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 26629-06 for ; Tue, 10 Jun 2003 16:05:19 -0300 (ADT) Received: from anchor-post-39.mail.demon.net (anchor-post-39.mail.demon.net [194.217.242.80]) by svr1.postgresql.org (Postfix) with ESMTP id B978030E364 for ; Tue, 10 Jun 2003 16:05:18 -0300 (ADT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-39.mail.demon.net with esmtp (Exim 3.36 #2) id 19PoQm-0007ZX-0U; Tue, 10 Jun 2003 20:05:16 +0100 Received: from localhost (localhost.localdomain [127.0.0.1]) by mainbox.archonet.com (Postfix) with ESMTP id 4D9B8162B1; Tue, 10 Jun 2003 20:05:15 +0100 (BST) Received: from client.archonet.com (client.archonet.com [192.168.1.16]) by mainbox.archonet.com (Postfix) with ESMTP id 6E81C162AC; Tue, 10 Jun 2003 20:05:14 +0100 (BST) Content-Type: text/plain; charset="iso-8859-1" From: Richard Huxton To: josh@agliodbs.com, pgsql-performance@postgresql.org Subject: Re: Re-ordering .CONF params ... questions for this list Date: Tue, 10 Jun 2003 20:05:11 +0100 User-Agent: KMail/1.4.3 References: <200306101101.46304.josh@agliodbs.com> In-Reply-To: <200306101101.46304.josh@agliodbs.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200306102005.11578.richardh@archonet.com> X-Virus-Scanned: by AMaViS snapshot-20020531 X-Archive-Number: 200306/37 X-Sequence-Number: 2121 On Tuesday 10 Jun 2003 7:01 pm, Josh Berkus wrote: > Folks, > > We've been discussing this for a while on HACKERS. However, I haven't be= en > getting much feedback on the specific order proposed. > > Attached is an outline of my proposed re-ordering of > postgresql.conf.sample. Please send me comments. I need to submit a patch > by Thursday, so don't take too long. > > This is an effort to make the order of run-time params in > postgresql.conf.sample and in the docs more logical and less baffling to > the new DBA. > > Questions: > 1) Should "enable_implicit_from" go in the "Version/Platform Compatibilit= y" > section where I have it now, or in "CLIENT CONNECTIONS-Statement Behavior= ", > or somewhere else? Version compatibility I'd vote for (hesitantly) > 2) Where should "preload_libraries" go? I'm very reluctant to start a > "Misc." section. Perhaps I should start a "LIBRARIES" section? No useful ideas - sorry. > 3) I have re-ordered each subsection somewhat. The fixed ordering is > based on: > a) My guess at the frequency with which that option will be > changed, with more common options toward the top of the subsection; > b) Grouping for tightly related options and for options that > cascade; c) where (a) and (b) are unclear, alpha order. > Does this order make sense looking at the file? Looks good, I'd suggest the following perhaps: Logging & Debugging I'd like this near the top, but then I use syslogging. With a new install I= go=20 in and check tcpip_socket etc, fix the logging and just see if everything i= s=20 working. Then I go in and do a little tuning. Actually, maybe the syslog sub-section should go above the others - say whe= re=20 you'll log to, and then what you'll log. Of course, I'm biased since I use= =20 syslog. Client Connection Defaults/Other/password_encryption This should probably go in the security section. Actually, looking at it=20 "dynamic_librar_path" is in the wrong place too - cut & past error? Query Tuning/Planner Method Enabling I'm in two minds here - obviously it is more "basic" than the "cost=20 constraints" section, but that's the one people will be tinkering with firs= t.=20 Nope - thinking about it, you've got it right. > 3) Should we use indenting in PostgreSQL.conf.sample? I tend to think it > would make the file easier to read, but I'm not sure what effect it would > have, if any, on parsing the file and whether other people would find it > easy to read. Not sure it would help that much - the comments need a URL to the relevant= =20 page in the online docs though. A couple more lines of comments too: # Syslog # To log to syslog, use something like # syslog =3D 2, syslog_facility =3D 'LOCAL0', syslog_ident =3D 'postgres' # Don't forget to update your syslog.conf then too. # ...etc Otherwise, looks good to me. --=20 Richard Huxton Archonet Ltd