Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 6FCBD2E0041 for ; Wed, 4 Jun 2008 10:01:12 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 23541-09 for ; Wed, 4 Jun 2008 10:00:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by developer.postgresql.org (Postfix) with ESMTP id EB4F72E00F0 for ; Wed, 4 Jun 2008 10:00:55 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id DF40B5649C; Wed, 4 Jun 2008 08:00:53 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Wed, 4 Jun 2008 08:00:50 -0500 Date: Wed, 4 Jun 2008 08:00:49 -0500 From: Decibel! To: Gregory Stark Cc: Josh Berkus , pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS Message-ID: <20080604130049.GG65238@decibel.org> References: <48409D1E.3070208@agliodbs.com> <16866.1212251015@sss.pgh.pa.us> <200805311144.38056.josh@agliodbs.com> <87tzgejmeh.fsf@oxford.xeocode.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9dgjiU4MmWPVapMU" Content-Disposition: inline In-Reply-To: <87tzgejmeh.fsf@oxford.xeocode.com> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:080604:stark@enterprisedb.com::/Uqf5osj1eBIoiOT:000000000000000 0000000000000000000000007EuA X-Hashcash: 1:20:080604:josh@agliodbs.com::PKZoXQXCZVJT6yN2:00000000000000000000 0000000000000000000000004DkO X-Hashcash: 1:20:080604:pgsql-hackers@postgresql.org::jqDNbsAvi1qFp4ep:000000000 0000000000000000000000007DBo X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/137 X-Sequence-Number: 119250 --9dgjiU4MmWPVapMU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 31, 2008 at 08:36:54PM +0100, Gregory Stark wrote: > > 4) By shifting from a model where postgresql.conf is document-formatted= and=20 > > hand-edited to one where it's machine generated, it becomes vastly easi= er to=20 > > write simple utilities to manage these settings. Right now, the big=20 > > "obstacle" to things like SET PERSISTENT is "how to we preseve the=20 > > hand-edited comments in the file" -- and the answer is we *don't.* =20 >=20 > What this sounds like is a sly way to try to get rid of postgresql.conf > entirely and replace it with parameters stored in the database so admins = would > adjust the parameters using an SQL syntax rather than a text file. >=20 > There are pros and cons of such a system but I think for newbie admins th= at > would be a thousand times *more* baffling. You would have to learn new > commands and have no holistic view of what parameters had been set, what > related parameters might exist. You also have no way to keep the file in a > version control system or sync across servers etc. It doesn't have to be in the database. I kinda like Oracle's method here; they default to storing config options in a binary file that (iirc) you can change via commands, but they also provide a way to turn that binary file into text (and back). That would allow for a lot of options when it comes to configuring stuff. --=20 Decibel!, aka Jim C. Nasby, Database Architect decibel@decibel.org=20 Give your computer some brain candy! www.distributed.net Team #1828 --9dgjiU4MmWPVapMU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFIRpIBdO30qud8SkgRArQVAJ4tiyrQOgL+3b1wwjuuN4i/tHL98ACfcIpd Uw/5k+5FJUVgcy1nnueFY3Q= =BTE6 -----END PGP SIGNATURE----- --9dgjiU4MmWPVapMU--