Re: unite recovery.conf and postgresql.conf

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Josh Berkus <josh@agliodbs.com>

Cc: pgsql-hackers@postgresql.org

Date: 2011-11-02T18:54:01Z

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 Wed, Nov 2, 2011 at 2:48 PM, Josh Berkus <josh@agliodbs.com> wrote:
> Is anyone working on SET PERSISTENT?  I thought that got bike-shedded to
> death.

I think we had a fairly good sketch of how it could work mapped out,
mostly based around adding a postgresql.auto file.  I could dig up the
old discussions, if need be.

Basically, I'd be willing to get that implemented and bull it through
to completion in time for 9.2 if having that would make it easier for
everyone to accept the idea of turning the recovery.conf parameters
into GUCs.  Otherwise I probably will not get to it this cycle.

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