Skip site navigation (1) Skip section navigation (2)

Re: Parsing config files in a directory

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Parsing config files in a directory
Date: 2009-10-28 21:08:00
Message-ID: 4AE8B2B0.1020008@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

Greg Smith wrote:
> On Wed, 28 Oct 2009, Josh Berkus wrote:
>
>> It's the basic and unsolvable issue of how do you have a file which is
>> both perfectly human-readable-and-editable *and* perfectly
>> machine-readable-and-editable at the same time.
>
> Let's see...if I remember correctly from the last two rounds of this 
> discussion, this is the point where someone pops up and says that 
> switching to XML for the postgresql.conf will solve this problem. 
> Whoever does that this time goes into the ring with Kevin and I, but 
> they don't get a club.  (All fight proceeds to benefit SPI of course).
>
>

That's precisely why I didn't get into this discussion (you guys are scary).

It really does seem like deja vu all over again. I'm usually good for a 
given argument once.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Hannu KrosingDate: 2009-10-28 21:26:23
Subject: Re: [PATCHES] updated hash functions for postgresql v1
Previous:From: Hannu KrosingDate: 2009-10-28 20:58:52
Subject: Re: [PATCHES] updated hash functions for postgresql v1

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group