Horton

Re: A smaller default postgresql.conf

Alvaro Herrera <alvherre@commandprompt.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Dave Page <dpage@pgadmin.org>
Cc: Joshua Drake <jd@commandprompt.com>, 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>, Hans-Juergen Schoenig <postgres@cybertec.at>
Date: 2008-08-20T12:51:06Z
Lists: pgsql-hackers 
Dave Page wrote:
> On Wed, Aug 20, 2008 at 4:40 AM, Joshua Drake <jd@commandprompt.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.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support