From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Parsing config files in a directory |
Date: | 2009-10-25 15:20:37 |
Message-ID: | 1997.1256484037@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> As a file point, I would prefer something like
> include 'whatever/*.conf'
> that is, listing the files as a glob pattern instead of naming a
> directory.
+1, but *only* if it does not lead to us having to write our own
version of glob(). It's not worth that much work, compared to just
allowing a directory name and hard-wiring the "*.conf" rule.
Some poking around suggests that glob(3) is reasonably portable
across Unixen, but is it provided on Windows?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Schmidt | 2009-10-25 15:34:26 | pg_standby doesnt't work |
Previous Message | Tom Lane | 2009-10-25 15:07:10 | Re: a question about relkind of RelationData handed over to heap_update function |