Re: Parsing config files in a directory

From: Kris Jurka <books(at)ejurka(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing config files in a directory
Date: 2009-10-26 21:49:37
Message-ID: alpine.BSO.2.00.0910261728060.27781@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 26 Oct 2009, Greg Stark wrote:

> Actually I think the include directory came from another use case
> which we've also discussed. Namely modules which need some
> configuration themselves. So for example when you install PostGIS it
> could drop a postgis.conf in the directory which you could then either
> edit yourself or override with SET PERSISTENT.

For modules that want to touch custom_variable_classes, they would still
need to touch the global config. While there was some discussion about
the ability to append/prepend/filter search_path, is there something
simpler (because order doesn't matter) we can do for
custom_variable_classes?

Kris Jurka

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2009-10-26 21:51:27 "toast.fillfactor" is documented but not recognized?
Previous Message Boszormenyi Zoltan 2009-10-26 21:46:20 GROUP BY bug or feature?