pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Fri, 6 Jun 2008 15:59:05 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0806061543200.7804@westnet.com> (raw)
In-Reply-To: <4848D447.10005@enterprisedb.com>
References: <Pine.GSO.4.64.0806041045520.2258@westnet.com>
	<29525.1212613052@sss.pgh.pa.us>
	<48472E47.7030701@dunslane.net>
	<Pine.GSO.4.64.0806042033120.3874@westnet.com>
	<20080605162400.GF16502@alvh.no-ip.org>
	<48481CBF.6040602@enterprisedb.com>
	<48481E3A.4010306@hagander.net>
	<Pine.GSO.4.64.0806051321360.27711@westnet.com>
	<20080605174209.GL16502@alvh.no-ip.org>
	<Pine.GSO.4.64.0806051452480.27254@westnet.com>
	<20080605212129.GI14498@yugib.highrise.ca>
	<Pine.GSO.4.64.0806051725550.10475@westnet.com>
	<3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.com>
	<4848D447.10005@enterprisedb.com>

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



view thread (226+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0806061543200.7804@westnet.com>
Permalink:  ../Pine.GSO.4.64.0806061543200.7804@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0806061543200.7804@westnet.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: gsmith@gregsmith.com, heikki@enterprisedb.com
  Subject: Re: Overhauling GUCS
  In-Reply-To: <Pine.GSO.4.64.0806061543200.7804@westnet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox