From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, 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-27 20:50:26 |
Message-ID: | alpine.GSO.2.01.0910271555040.23266@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 27 Oct 2009, Greg Stark wrote:
> If they all had to edit the same file then they have to deal with
> writing out values and also reading them back. Everyone would need a
> config file parser and have to make deductions about what other tools
> were trying to do and how to interact with them.
Exactly, that's the situation we're trying to escape from now in a
nutshell.
To answer Tom's question about providing better guidelines for tool
authors, I was hoping to provide the first such tool and submit a patch
for refactoring initdb using the same approach before 8.5 is done. I'd
rather see that nailed down with a concrete proof of concept attached that
implements a candidate approach by example rather than to just talk about
it in general. I don't think that needs to hold up work on this patch
though, particularly given that I'm dependent on this one being committed
for my plan to work.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-10-27 21:05:45 | Re: Endgame for all those SELECT FOR UPDATE changes: fix plan node order |
Previous Message | Tom Lane | 2009-10-27 20:42:32 | Re: Endgame for all those SELECT FOR UPDATE changes: fix plan node order |