| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, Joshua Drake <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, Hans-Juergen Schoenig <postgres(at)cybertec(dot)at> |
| Subject: | Re: A smaller default postgresql.conf |
| Date: | 2008-08-20 13:02:49 |
| Message-ID: | 48AC15F9.4020606@hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Dave Page wrote:
>> On Wed, Aug 20, 2008 at 4:40 AM, Joshua Drake <jd(at)commandprompt(dot)com> wrote:
>
>>> I am not arguing for this but if we went down that route it does buy us
>>> the ability to compartmentalize the entire conf.. so you have:
>>>
>>> memory_settings.conf
>>> logging.conf
>>> maintenance.conf
>> Would make it damn hard for pgAdmin to figure out how to edit the
>> config though. That's why we only support single-file configs atm.
>
> That's why we're working on adding a "sourcefile" attribute to GUC, so
> that it's trivial to know the path of the config file each settings
> comes from.
Still won't make life very easy for pgadmin, but it will make it
slightly less difficult.
That said, I think splitting the config out like that will mkae it even
more confusing for the newbie user, which is contrary to what we want here.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2008-08-20 13:16:56 | Re: Patch: plan invalidation vs stored procedures |
| Previous Message | Tom Lane | 2008-08-20 13:01:51 | Re: Extending varlena |