From: Andrew Dunstan <andrew@dunslane.net>
To: Greg Sabino Mullane <greg@turnstep.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Sat, 31 May 2008 21:41:55 -0400
Message-ID: <4841FE63.1020708@dunslane.net> (raw)
In-Reply-To: <16ab21af4a6ad3385411e4178dcc1416@biglumber.com>
References: <16ab21af4a6ad3385411e4178dcc1416@biglumber.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew@dunslane.net, greg@turnstep.com
Subject: Re: Overhauling GUCS
In-Reply-To: <4841FE63.1020708@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox