| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, Gregory Stark <stark(at)enterprisedb(dot)com>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca> |
| Subject: | Re: Permanent settings |
| Date: | 2008-02-20 20:43:14 |
| Message-ID: | 47BC90E2.4040505@hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-20 20:45:27 | Re: Permanent settings |
| Previous Message | Tom Lane | 2008-02-20 20:39:24 | Re: Permanent settings |