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: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org, Josh Berkus <josh@agliodbs.com>
Subject: Re: Overhauling GUCS
Date: Mon, 2 Jun 2008 12:22:21 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0806021206500.4018@westnet.com> (raw)
In-Reply-To: <17932.1212415926@sss.pgh.pa.us>
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>

On Mon, 2 Jun 2008, Tom Lane wrote:

> Greg Smith <gsmith@gregsmith.com> writes:
>> Joshua has been banging a drum for a while now that all this data needs to
>> get pushing into the database itself.
>
> This is, very simply, not going to happen.

Right, there are also technical challenges in the way of that ideal.  I 
was only mentioning the reasons why it might not be the best idea even if 
it were feasible.  However, I do not see why the limitations you bring up 
must get in the way of thinking about how to interact and manage the 
configuration data in a database context, even though it ultimately must 
be imported and exported to a flat file.

The concerns you bring up again about leaving the database in an 
unstartable state are a particularly real danger in the "only has access 
to 5432" hosted provider case that this redesign is trying to satisfy.  I 
added a "Gotchas" section to the wiki page so that this issue doesn't get 
forgotten about.  The standard way to handle this situation is to have a 
known good backup configuration floating around.  Adding something in that 
area may end up being a hard requirement before remote editing makes 
sense.

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



view thread (226+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0806021206500.4018@westnet.com>
Permalink:  ../Pine.GSO.4.64.0806021206500.4018@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0806021206500.4018@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, peter_e@gmx.net, josh@agliodbs.com
  Subject: Re: Overhauling GUCS
  In-Reply-To: <Pine.GSO.4.64.0806021206500.4018@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