From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: Decibel! <decibel@decibel.org>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org, Josh Berkus <josh@agliodbs.com>
Subject: Re: Overhauling GUCS
Date: Wed, 04 Jun 2008 16:57:32 -0400
Message-ID: <29525.1212613052@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.4.64.0806041045520.2258@westnet.com>
References: <48409D1E.3070208@agliodbs.com>
<200806010032.53337.peter_e@gmx.net>
<Pine.GSO.4.64.0806020452220.26912@westnet.com>
<17932.1212415926@sss.pgh.pa.us>
<20080604131810.GH65238@decibel.org>
<4846A483.8000001@pse-consulting.de>
<Pine.GSO.4.64.0806041045520.2258@westnet.com>
Greg Smith <gsmith@gregsmith.com> writes:
> On Wed, 4 Jun 2008, Andreas Pflug wrote:
>> IMHO the best compromise in machine and human readability is an XML format.
> If the primary PostgreSQL configuration file becomes XML I will quit
> working with the project. I'm not kidding.
I have no particular use for XML in this scenario either, but really
this thread seems to be arguing about mostly-irrelevant details. There
is not anything fundamentally broken about keeping configuration in a
text file, as is proven by the fact that all those other packages do it.
The real problem we need to solve is how to allow newbies to have the
system auto-configured to something that more or less solves their
problems. Putting the config settings in XML does not accomplish that,
and neither does putting them inside the database. It might knock a
day or two off the time needed to develop a tool that actually does
solve the newbie's problem ... but it's unlikely that the effort of
changing Postgres to use some other configuration representation would
get repaid through easier tool development.
So I think we should stop worrying about the file format and think about
these two problems:
* Can we present the config options in a more helpful way (this is 99%
a documentation problem, not a code problem)?
* Can we build a "configuration wizard" to tell newbies what settings
they need to tweak?
regards, tom lane
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: tgl@sss.pgh.pa.us, gsmith@gregsmith.com, pgadmin@pse-consulting.de, decibel@decibel.org, peter_e@gmx.net, josh@agliodbs.com
Subject: Re: Overhauling GUCS
In-Reply-To: <29525.1212613052@sss.pgh.pa.us>
* 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