pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Fri, 6 Jun 2008 21:02:25 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0806062044110.1985@westnet.com> (raw)
In-Reply-To: <8459.1212798641@sss.pgh.pa.us>
References: <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>
	<20080605174209.GL16502@alvh.no-ip.org>
	<Pine.GSO.4.64.0806051452480.27254@westnet.com>
	<20080605212129.GI14498@yugib.highrise.ca>
	<Pine.GSO.4.64.0806051725550.10475@westnet.com>
	<3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.com>
	<4848FAA6.8000903@pse-consulting.de>
	<87ej7aeuqx.fsf@oxford.xeocode.com>
	<4849137C.3040008@pse-consulting.de>
	<877id2erp6.fsf@oxford.xeocode.com>
	<48492356.4040506@pse-consulting.de>
	<1618.1212765176@sss.pgh.pa.us>
	<Pine.GSO.4.64.0806061524140.7804@westnet.com>
	<87d4muclr6.fsf@oxford.xeocode.com>
	<Pine.GSO.4.64.0806061730410.27291@westnet.com>
	<8459.1212798641@sss.pgh.pa.us>

On Fri, 6 Jun 2008, Tom Lane wrote:

> Well, you can't see the default or reset values in pg_settings, only the
> current value.  However, I fail to see the use of either of those for
> a configure wizard.

I'm under the impression that the primary reason to put the default in 
there is to make it easier for a file generator program to be decoupled a 
bit from the internal representation.  Regardless, these values should be 
exposed for tool writers.  If you build a prototype interface for an 
interactive settings changing tool, you quickly discover that showing the 
default, range, and recommended setting are all valuable things people 
would like to see when deciding what the change a setting to.  And there's 
no reason accumulating all that info should be the responsibility of a 
tool writer when it's easy to expose and keep up to date inside the 
database itself.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD



view thread (226+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0806062044110.1985@westnet.com>
Permalink:  ../Pine.GSO.4.64.0806062044110.1985@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0806062044110.1985@westnet.com

 · 

reply
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: gsmith@gregsmith.com, tgl@sss.pgh.pa.us
  Subject: Re: Overhauling GUCS
  In-Reply-To: <Pine.GSO.4.64.0806062044110.1985@westnet.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