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 [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
