From: Josh Berkus <josh@agliodbs.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Jignesh K. Shah <J.K.Shah@sun.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Mon, 2 Jun 2008 11:06:04 -0700
Message-ID: <200806021106.05833.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0806021227100.4018@westnet.com>
References: <48409D1E.3070208@agliodbs.com>
<484418D9.5040608@sun.com>
<Pine.GSO.4.64.0806021227100.4018@westnet.com>
Greg,
> Like some of the other GUC simplification ideas that show up sometimes
> (unifying all I/O and limiting background processes based on that total
> is another), this is hard to do internally. Josh's proposal has a fair
> amount of work involved, but the code itself doesn't need to be clever
> or too intrusive. Unifying all the memory settings would require being
> both clever and intrusive, and I doubt you'll find anybody who could
> pull it off who isn't already overtasked with more important
> improvements for the 8.4 timeframe.
Plus, I'm a big fan of "enable an API" rather than "write a feature". I
think that there are people & companies out there who can write better
autotuning tools than I can, and I'd rather give them a place to plug
those tools in than trying to write autotuning into the postmaster.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
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: josh@agliodbs.com, gsmith@gregsmith.com, J.K.Shah@sun.com
Subject: Re: Overhauling GUCS
In-Reply-To: <200806021106.05833.josh@agliodbs.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