Re: unite recovery.conf and postgresql.conf

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Joshua Berkus <josh@agliodbs.com>

Cc: pgsql-hackers@postgresql.org, Tatsuo Ishii <ishii@postgresql.org>

Date: 2011-09-25T15:58:22Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Restructure error handling in reading of postgresql.conf.
- d56b3afc0376 9.2.0 cited

On Sat, Sep 24, 2011 at 3:49 PM, Joshua Berkus <josh@agliodbs.com> wrote:
>> Since we haven't yet come up with a reasonable way of machine-editing
>> postgresql.conf, this seems like a fairly serious objection to
>> getting
>> rid of recovery.conf.  I wonder if there's a way we can work around
>> that...
>
> Well, we *did* actually come up with a reasonable way, but it died under an avalanche of bikeshedding and "we-must-do-everything-the-way-we-always-have-done".  I refer, of course, to the "configuration directory" patch, which was a fine solution, and would indeed take care of the recovery.conf issues as well had we implemented it.  We can *still* implement it, for 9.2.

Well, I find that a fairly ugly solution to the problem, but I agree
that it is solvable, if we could get a critical mass on any some
particular solution.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company