Horton

Re: A smaller default postgresql.conf

Dave Page <dpage@pgadmin.org>

View thread View on postgr.es
From: "Dave Page" <dpage@pgadmin.org>
To: "Joshua Drake" <jd@commandprompt.com>
Cc: "Tom Lane" <tgl@sss.pgh.pa.us>, "Bruce Momjian" <bruce@momjian.us>, "Robert Treat" <xzilla@users.sourceforge.net>, pgsql-hackers@postgresql.org, "Peter Eisentraut" <peter_e@gmx.net>, "Magnus Hagander" <magnus@hagander.net>, "Alvaro Herrera" <alvherre@commandprompt.com>, "Hans-Juergen Schoenig" <postgres@cybertec.at>
Date: 2008-08-20T08:05:57Z
Lists: pgsql-hackers 
On Wed, Aug 20, 2008 at 4:40 AM, Joshua Drake <jd@commandprompt.com> wrote:
> On Tue, 19 Aug 2008 23:32:34 -0400
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>> Bruce Momjian <bruce@momjian.us> writes:
>> > On idea is for postgresql.conf to merely include other files:
>> >     include 'sharedmem.conf'
>> >     include 'compat.conf'
>> >     ...
>>
>> That would definitely add complexity ... what would it buy in return?
>
> 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.

-- 
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com