| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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>, 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 20:40:17 |
| Message-ID: | 4AE60931.3080004@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/26/09 9:01 AM, Robert Haas wrote:
>> (BTW, why do we actually need an includedir mechanism for this?
>> > A simple include of a persistent.conf file seems like it would be
>> > enough.)
>
> I was starting to wonder that, too.
Different issue, really, which is that some people (including me) would
like to break up PostgreSQL configuration into 7 or 8 files based on
functional area (e.g. memory.conf, logging.conf, custom_options.conf
...). I do this with my Apache configs, and find it vastly more
manageable than one big file, especially under SCM. If I write a
config management tool, my tool will also do this.
That's the reason for the dir, not persistent.conf, which I agree could
be a single file.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-10-26 20:56:28 | Re: table corrupted |
| Previous Message | Tom Lane | 2009-10-26 20:33:37 | Re: Parsing config files in a directory |