Re: unite recovery.conf and postgresql.conf

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>

To: Tatsuo Ishii <ishii@postgresql.org>

Cc: pgsql-hackers@postgresql.org

Date: 2011-09-24T00:30:35Z

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

> I'm not sure what you mean by "not deal with" but part of pgpool-II's
> functionality assumes that we can easily generate recovery.conf. If
> reconf.conf is integrated into postgresql.conf, we need to edit
> postgresql.conf, which is a little bit harder than generating
> recovery.conf, I think.

Oh?  Clearly I've been abusing pgPool2 then.  Where's the code that
generates that?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com