Re: Permanent settings - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Permanent settings
Date
Msg-id 47BC90E2.4040505@hagander.net
Whole thread Raw
In response to Re: Permanent settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Permanent settings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> On Wed, Feb 20, 2008 at 01:43:46PM -0500, Tom Lane wrote:
>>> The main part of that is the GUI, which is certainly not going to be in
>>> the server, so I fail to see exactly what you think you're really
>>> gaining.
> 
>> The way things are now, writing the GUI is *simple* compared to the fact
>> that you have to write a config file parser. One for each tool.
> 
> No you don't.  All you need is the output of the pg_settings view.
> Or at least, if that's insufficient, let's discuss exactly how.

I can read the settings. How do I write them, if the only interface to 
write them is to deal with the file as a complete unit?

I was certainly planning to use the output of the pg_settings view to 
read the data. pgadmin today uses the config file, which is one reason 
it sucks :-) (because it basically presents the entire config file as a 
remote text-file editor to the user, and that's not what the user wants)

//Magnus


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Permanent settings
Next
From: Tom Lane
Date:
Subject: Re: Permanent settings