Re: Parsing config files in a directory

From: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
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 10:29:34
Message-ID: 1d4e0c10910250329k623e5d8fnb45afae9386084a4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 25, 2009 at 10:08 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> As a file point, I would prefer something like
>
> include 'whatever/*.conf'

+1 for that. That's what Apache does and it works well for the users
and the packagers.

--
Guillaume

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 노홍찬 2009-10-25 14:28:49 a question about relkind of RelationData handed over to heap_update function
Previous Message James Mansion 2009-10-25 10:27:17 Re: Could postgres be much cleaner if a future release skipped backward compatibility?