Re: unite recovery.conf and postgresql.conf

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Joshua Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Tatsuo Ishii <ishii(at)postgresql(dot)org>
Subject: Re: unite recovery.conf and postgresql.conf
Date: 2011-09-25 15:58:22
Message-ID: CA+Tgmoad81=i=r-5emz1itMg9ymQ0P7vG6ROqPw-540tmrvXWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Sep 24, 2011 at 3:49 PM, Joshua Berkus <josh(at)agliodbs(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-09-25 16:01:36 Re: Inserting heap tuples in bulk in COPY
Previous Message Robert Haas 2011-09-25 15:52:47 Re: [v9.2] Fix Leaky View Problem