From: | dpage(at)pgadmin(dot)org |
---|---|
To: | "Magnus Hagander" <magnus(at)hagander(dot)net> |
Cc: | "Gregory Stark" <stark(at)enterprisedb(dot)com>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Overhauling GUCS |
Date: | 2008-08-18 21:34:49 |
Message-ID: | 937d27e10808181434oe3cc9f5u79301d44e3c6bd92@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/18/08, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Dave Page wrote:
>> On Mon, Aug 18, 2008 at 8:51 PM, Gregory Stark <stark(at)enterprisedb(dot)com>
>> wrote:
>>> The main problem that I've seen described is what I mentioned before:
>>> allowing
>>> adjusting the postgresql.conf GUC settings by remote users who don't have
>>> shell access.
>>
>> Which pgAdmin has done perfectly well for years, as long as the config
>> is all in one file.
>
> I'll argue it's not done it perfectly well (it's not particularly
> user-friendly), but it has certainly *done* it...
I mean it's able to read & write the config file correctly. I agree
the ui is, umm, sub-optimal.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-08-18 21:50:10 | Re: Overhauling GUCS |
Previous Message | David Fetter | 2008-08-18 21:32:49 | Re: Extending varlena |