From: Alvaro Herrera <alvherre@commandprompt.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Thu, 5 Jun 2008 13:42:09 -0400
Message-ID: <20080605174209.GL16502@alvh.no-ip.org> (raw)
In-Reply-To: <Pine.GSO.4.64.0806051321360.27711@westnet.com>
References: <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>
<Pine.GSO.4.64.0806042033120.3874@westnet.com>
<20080605162400.GF16502@alvh.no-ip.org>
<48481CBF.6040602@enterprisedb.com>
<48481E3A.4010306@hagander.net>
<Pine.GSO.4.64.0806051321360.27711@westnet.com>
Greg Smith wrote:
> On Thu, 5 Jun 2008, Magnus Hagander wrote:
>
>> We really need a "proper API" for it, and the stuff in pgAdmin isn't
>> even enough to base one on.
>
> I would be curious to hear your opinion on whether the GUC overhaul
> discussed in this thread is a useful precursor to building such a proper
> API.
I must say that I am confused by this thread. What's the discussed GUC
overhaul? Things that I vaguely recall being proposed are (in the order
they came to mind):
(1) Add a lot more comments to each setting
(2) Add documentation links to each setting
(3) Move more frequently used settings to the top of the file
(4) Ship different sample config files
(5) Create an expert system to suggest tuning
(6) Other random ideas (XML, settings in database, others?)
To me, there are two ideas that are doable right now, which are (2) and
(4). (1) seems to be a step backwards in pg_hba.conf experience, and we
would have to maintain duplicate documentation. (3) seems messy. (5)
is a lot of work; do we have volunteers? As for (6), the two examples I
give can be easily dismissed.
(2) and (4) do not seem necessary to get the config API built.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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: alvherre@commandprompt.com, gsmith@gregsmith.com, magnus@hagander.net, heikki@enterprisedb.com
Subject: Re: Overhauling GUCS
In-Reply-To: <20080605174209.GL16502@alvh.no-ip.org>
* 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