Re: Parsing config files in a directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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-24 23:38:38
Message-ID: 15560.1256427518@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Supporting an include-directory seems harmless to me, and even
> potentially useful. But the only way to solve the problem of
> machine-parsing the config file is to remove the instructions (which
> can only EVER be parsed by human beings) and put them somewhere else.

Uh, that is complete nonsense. The instructions are not a problem.
The ability to have comments at all might be thought to be a problem,
but removing it isn't going to be an acceptable solution.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2009-10-25 00:02:16 Re: Parsing config files in a directory
Previous Message Tom Lane 2009-10-24 23:16:30 WIP patch: EvalPlanQual rewrite