| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | 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 20:08:19 |
| Message-ID: | alpine.GSO.2.01.0910281559210.18553@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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).
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-10-28 20:11:44 | Re: Parsing config files in a directory |
| Previous Message | Tom Lane | 2009-10-28 19:57:12 | Re: [PATCHES] updated hash functions for postgresql v1 |