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: Bruce Momjian <bruce@momjian.us>, Simon Riggs <simon@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2011-11-07T19:34:18Z

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 Mon, Nov 7, 2011 at 2:14 PM, Josh Berkus <josh@agliodbs.com> wrote:
> 2. standby_mode becomes an ENUM: "off,standby,pitr".  It can be reset on
> server reload or through "pg_ctl promote"

I'm a little bit confused by the way we're dragging standby_mode into
this conversation.  If you're using pg_standby, you can set
standby_mode=off and still have a standby.  If you're using a simple
recovery command that just copies files, you need to set
standby_mode=on if you don't want the standby to exit recovery and
promote.  But I think of standby_mode as meaning "should we use the
internal standby loop rather than depending on an external tool?"
rather than "should we become a standby?".

Maybe I'm confused.

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