Message-ID: <4841FE63.1020708@dunslane.net>
Date: Sat, 31 May 2008 21:41:55 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text
	SeaMonkey/1.0.9
MIME-Version: 1.0
To: Greg Sabino Mullane <greg@turnstep.com>
CC: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
References: <16ab21af4a6ad3385411e4178dcc1416@biglumber.com>
In-Reply-To: <16ab21af4a6ad3385411e4178dcc1416@biglumber.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Greg Sabino Mullane wrote:
>
> * A weak +1 to the #include idea. I'm much more inclined to simply
> add a new section to the bottom of the file and use version
> control, but I could see ways in which include would be useful.
>
>
>
>   

We already have include directives, and have had since 8.2.

Thus spake the docs:

"In addition to parameter settings, the postgresql.conf file can contain 
/include directives/, which specify another file to read and process as 
if it were inserted into the configuration file at this point. Include 
directives simply look like:

include 'filename'

If the file name is not an absolute path, it is taken as relative to the 
directory containing the referencing configuration file. Inclusions can 
be nested."


cheers

andrew