From: Stephen R. van den Berg <srb@cuci.nl>
To: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Mon, 2 Jun 2008 14:35:48 +0200
Message-ID: <20080602123548.GA1590@cuci.nl> (raw)
In-Reply-To: <Pine.GSO.4.64.0806020452220.26912@westnet.com>
References: <48409D1E.3070208@agliodbs.com>
<200806010032.53337.peter_e@gmx.net>
<Pine.GSO.4.64.0806020452220.26912@westnet.com>
Greg Smith wrote:
>Joshua has been banging a drum for a while now that all this data needs to
>get pushing into the database itself. The GUCS data is clearly structured
>tables, you'll open up the potential to add a whole new class of
>user-friendly applications for making configuration easier to manage.
>However, I don't fully agree with taking that idea as far as Joshua has
>suggested (only having the config data in the database), because having
>everything in a simple text file that can be managed with SCM etc. has
>significant value. It's nice to allow admins to be able to make simple
>changes with just a file edit. It's nice that you can look at all the
>parameters in one place and browse them. However, I do think that the
>internal database representation must be capable of holding everything in
>the original postgresql.conf file and producing an updated version of the
>file, either locally or remotely, as needed.
Depending on the complexity you want to have inside the generator, one
could imagine a middle ground solution like:
include "database-generated.conf"
include "local-overrides.conf"
Where the "database-generated.conf" does not necessarily needs a lot of
comments.
>Josh has the actual brains behind such an app all planned out if you look
>at his presentations, but without the larger overhaul it's just not
>possible to make the implementation elegant.
IMHO Greg's response is the most comprehensive and well-thought-through
contribution in the whole GUC thread.
--
Sincerely,
Stephen R. van den Berg.
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: srb@cuci.nl
Subject: Re: Overhauling GUCS
In-Reply-To: <20080602123548.GA1590@cuci.nl>
* 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