Re: Parsing config files in a directory

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: jd(at)commandprompt(dot)com
Cc: Thom Brown <thombrown(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, 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-29 15:34:38
Message-ID: 4AE9B60E.5010005@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> On Thu, 2009-10-29 at 12:31 +0000, Thom Brown wrote:
>
>> 2009/10/29 Andrew Dunstan <andrew(at)dunslane(dot)net>:
>>
>
>
>>> Why not allow something like += or .= instead of the = to denote appending
>>> to a list?
>>>
>>> custom_variable_classes += 'x'
>>>
>>> seems a whole lot nicer to me.
>>>
>>>
>> I would see that as making the config more programatic so while that
>> might not look too weird to a developer, it could be confusing for a
>> DBA or system administrator. I don't think that's how config files
>> should work, and it also adds gotchas like the following.
>>
>>
>
> The DBAs I know would think we were absolutely off our rocker for such a
> thing. At least it would make great humor at presentations.
>
>
>

The whole config file is a joke. We'd never do it the way we do if we
were designing it from scratch, but we seem to be incapable of biting
the bullet and replacing it with something sane, which is why I have
ignored most of the current debate.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-10-29 15:38:07 Re: Parsing config files in a directory
Previous Message Robert Haas 2009-10-29 15:18:47 Re: Parsing config files in a directory