From: Steve Atkins <steve@blighty.com>
To: PostgreSQL Developers <pgsql-hackers@postgresql.org>
Subject: Re: Overhauling GUCS
Date: Sun, 17 Aug 2008 15:49:24 -0700
Message-ID: <F907F453-0733-4070-9F4B-211ABF6C8038@blighty.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0808171610220.22642@westnet.com>
References: <7473.1212625397@sss.pgh.pa.us>
<200807161530.m6GFUNY28751@momjian.us>
<407fa4640808130738s3537ca45j22322a5eb70f9173@mail.gmail.com>
<Pine.GSO.4.64.0808171610220.22642@westnet.com>
On Aug 17, 2008, at 1:48 PM, Greg Smith wrote:
> On Wed, 13 Aug 2008, Michael Nacos wrote:
>
>> Hi there... Configuration autotuning is something I am really
>> interested in.
>> I have seen this page: http://wiki.postgresql.org/wiki/
>> GUCS_Overhaul and
>> a couple of emails mentioning this, so I wanted to ask is someone
>> already
>> on it? If yes, I'd like to contribute.
>
> Good time to give a status report on what's been going on with all
> this.
>
> With some help I just finished off an answer to problem #1 there
> recently, "Most people have no idea how to set these". There was
> some concern here that work was being done on config tools without a
> clear vision of what was going to be tuned. See http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
> for an intro on how to set the 18 most important parameters (+7
> logging parameters) based on the best information I'm aware of.
>
> Circa June, Steve Atkins was looking into writing a C++/Qt GUI
> tuning interface application, with the idea that somebody else would
> figure out the actual smarts to the tuning effort. Don't know where
> that's at.
First pass is done. Needs a little cleanup before sharing. I spent a
fair while down OS-specific-hardware-queries rathole, but I'm better
now.
Cheers,
Steve
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: steve@blighty.com
Subject: Re: Overhauling GUCS
In-Reply-To: <F907F453-0733-4070-9F4B-211ABF6C8038@blighty.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