From: Greg Smith <gsmith@gregsmith.com>
To: Michael Nacos <m.nacos@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Mon, 18 Aug 2008 13:39:45 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0808181250190.17947@westnet.com> (raw)
In-Reply-To: <407fa4640808180426q26a41cv817deb91dbbcd312@mail.gmail.com>
References: <7473.1212625397@sss.pgh.pa.us>
<200807161530.m6GFUNY28751@momjian.us>
<407fa4640808130738s3537ca45j22322a5eb70f9173@mail.gmail.com>
<Pine.GSO.4.64.0808171610220.22642@westnet.com>
<407fa4640808180426q26a41cv817deb91dbbcd312@mail.gmail.com>
On Mon, 18 Aug 2008, Michael Nacos wrote:
> Having done a SELECT * FROM pg_settings, all the information you need
> seems to be there...
See http://archives.postgresql.org/pgsql-hackers/2008-06/msg00209.php You
sound like you're at rung 2 on the tool author ladder I describe there,
still thinking about the fun part of tuning but not yet aware of the
annoying postgresql.conf management issues that show up in the field that
motivate many of the GUCS changes suggested. Coping with user and
system-generated comments is one difficult part that people normally don't
consider, dealing with bad settings the server won't start with is
another.
I did make one mistake in that message, which is that the "context" field
of pg_settings already exposes when a setting can be changed. And it is
possible to get the value for a setting as entered by the admin by joining
pg_settings against what current_setting returns, which is one part of
handling the import/change/export cycle while keeping useful units intact.
> Maybe I'm being over-simplistic here, but the important bit is knowing
> how you should tune stuff - and this is what I'm hoping to learn through
> this process.
The tuning references at the bottom of
http://wiki.postgresql.org/wiki/GUCS_Overhaul provide more detail here
than anyone has been able to automate so far. There's certainly room to
improve on the suggestions there with some introspection of the database,
I'm trying to stay focused on something to help newbies whose settings are
completely wrong first.
> As soon as there is a tuning strategy published, a number of tools will
> certainly follow.
Josh Berkus published one in 2005 and zero such tools have been produced
since then, even though it looked to him then (like it does to you now and
like it did to me once) that such a tool would easily follow:
http://pgfoundry.org/docman/?group_id=1000106
The bright side here is that you don't have to waste time tinkering in
this area to find out where the dead ends are like Josh and I
independantly did.
--
* 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, m.nacos@gmail.com
Subject: Re: Overhauling GUCS
In-Reply-To: <Pine.GSO.4.64.0808181250190.17947@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