Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 621FE2E0049 for ; Fri, 6 Jun 2008 16:59:12 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 27546-04 for ; Fri, 6 Jun 2008 16:59:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from westnet.com (westnet.com [216.187.52.2]) by developer.postgresql.org (Postfix) with ESMTP id 9A1912E0041 for ; Fri, 6 Jun 2008 16:59:07 -0300 (ADT) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id m56Jx5GD001624; Fri, 6 Jun 2008 15:59:05 -0400 (EDT) Received: from localhost (gsmith@localhost) by westnet.com (8.14.0/8.13.2/Submit) with ESMTP id m56Jx5BM001620; Fri, 6 Jun 2008 15:59:05 -0400 (EDT) X-Authentication-Warning: westnet.com: gsmith owned process doing -bs Date: Fri, 6 Jun 2008 15:59:05 -0400 (EDT) From: Greg Smith X-X-Sender: gsmith@westnet.com To: Heikki Linnakangas cc: pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS In-Reply-To: <4848D447.10005@enterprisedb.com> Message-ID: References: <29525.1212613052@sss.pgh.pa.us> <48472E47.7030701@dunslane.net> <20080605162400.GF16502@alvh.no-ip.org> <48481CBF.6040602@enterprisedb.com> <48481E3A.4010306@hagander.net> <20080605174209.GL16502@alvh.no-ip.org> <20080605212129.GI14498@yugib.highrise.ca> <3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.com> <4848D447.10005@enterprisedb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/316 X-Sequence-Number: 119429 On Fri, 6 Jun 2008, Heikki Linnakangas wrote: > Or perhaps we should explicitly mark the settings the tool has generated, and > comment out: > > #shared_buffers = 32MB # commented out by wizard on 2008-06-05 > shared_buffers = 1024MB # automatically set by wizard on 2008-06-05 What I would like to do is make the tool spit out a revision history in the same way I find all "big IT" shops handling this already: by putting a revision history style commentary above the current setting. Here's a sample: # 2008-03-02 : 32MB : postgres : Database default # 2008-05-02 : 512MB : pg_autotune : Wizard update # 2008-05-15 : 1024MB : gsmith : Increased after benchmark tests shared_buffers = 1024MB If the first tuning tool that comes into existance used this format, and the format was reasonable, I think it would be possible to get people making manual edits to adopt it as well. The exact details of how this should look are off-topic for the main discussion here, though, so I'd prefer if this whole line of discussion died off. Anyone who wants to comment on this whole area, feel free to contact me off-list or edit the Wiki page (which has a section on this topic now) to hash out suggestions in this area, I'm trying to keep this somewhat thread focused now. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD