From: Greg Smith <gsmith@gregsmith.com>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Thu, 5 Jun 2008 04:15:49 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0806050352530.10308@westnet.com> (raw)
In-Reply-To: <48478D8F.1030006@enterprisedb.com>
References: <Pine.GSO.4.64.0806020452220.26912@westnet.com>
<17932.1212415926@sss.pgh.pa.us>
<20080604131810.GH65238@decibel.org>
<4846A483.8000001@pse-consulting.de>
<Pine.GSO.4.64.0806041045520.2258@westnet.com>
<29525.1212613052@sss.pgh.pa.us>
<48472E47.7030701@dunslane.net>
<7473.1212625397@sss.pgh.pa.us>
<20080605011455.GF14498@yugib.highrise.ca>
<Pine.GSO.4.64.0806042134090.3874@westnet.com>
<20080605023720.GG14498@yugib.highrise.ca>
<Pine.GSO.4.64.0806042241070.23557@westnet.com>
<48478D8F.1030006@enterprisedb.com>
On Thu, 5 Jun 2008, Heikki Linnakangas wrote:
> A configuration wizard would be nice, but it would be a good start to add a
> section to the manual on how to do the basic tuning. AFAICS we don't have
> one. Clear instructions on how to set the few most important settings like
> shared_buffers and checkpoint_timeout/segments would probably be enough, with
> a link to the main configuration section that explains the rest of the
> settings.
It hasn't gelled yet but I'm working on that. Most of the text needed is
now linked to at http://wiki.postgresql.org/wiki/Performance_Optimization
I already talked with Chris Browne about merging his document I put first
in that list with useful pieces from some of mine into one more
comprehensive document on the Wiki, covering everything you mention here.
If we took a snapshot of that when it's done and dumped that into the
manual, I don't think that would be a problem to wrap up before 8.4 is
done. I'd like to include a link to the above performance page in that
section of the manual as well, both so that people are more likely to find
fresh content as well as to give them pointers toward more resources than
the manual can possibly cover.
> If people don't read the manual, we can add a link to it from
> postgresql.conf.sample, add a screen to the Windows installer suggesting
> to read it, or even open postgresql.conf in Notepad.
They don't. Putting pointers toward a relatively simple performance
tuning document a bit more in people's faces might help lower some of the
criticism the project takes over providing low defaults for so many
things.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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.0806050352530.10308@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