| From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Configuration include directory |
| Date: | 2011-12-13 23:19:47 |
| Message-ID: | 4EE7DD93.2030100@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/13/2011 03:22 PM, Peter Eisentraut wrote:
> Well, the existing include directive works relative to the directory the
> including file is in. If includedir works differently from that, that
> would be highly confusing.
>
Right, and that's gone now; latest update matches the regular include
behavior.
> I would actually just extend "include" to accept wildcards instead of
> inventing a slightly new and slightly different mechanism.
>
That's one of the ideas thrown out during the first round of discussion
around this patch. Tom's summary of why that wasn't worth doing hits
the highlights:
http://archives.postgresql.org/pgsql-hackers/2009-10/msg01628.php
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2011-12-13 23:30:34 | NOTIFY with tuples |
| Previous Message | Alexander Shulgin | 2011-12-13 22:45:08 | Re: WIP: URI connection string support for libpq |