From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: unite recovery.conf and postgresql.conf |
Date: | 2011-11-07 19:34:18 |
Message-ID: | CA+TgmoaT5=cV06ZSD4uJEWhLzTh44mn7+wGeqqGrhp0Fd2p1Tg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 7, 2011 at 2:14 PM, Josh Berkus <josh(at)agliodbs(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2011-11-07 19:34:51 | Re: GiST for range types (was Re: Range Types - typo + NULL string constructor) |
Previous Message | Josh Berkus | 2011-11-07 19:14:34 | Re: unite recovery.conf and postgresql.conf |