On Thu, Mar 12, 2015 at 11:53 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2015-03-12 15:52:02 +0100, Andres Freund wrote:
I guess what you actually intended to test was StandbyModeRequested?
Err, EnableHotStandby.
Pushed the fix.
Regards,
--
Fujii Masao
--
Sent via pgsql-hackers
On Thu, Mar 12, 2015 at 11:53 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2015-03-12 15:52:02 +0100, Andres Freund wrote:
I guess what you actually intended to test was StandbyModeRequested?
Err, EnableHotStandby.
Indeed. Without !EnableHotStandby, a node in recovery would simply be
On 13/03/15 15:06, Petr Jelinek wrote:
On 12/03/15 15:53, Andres Freund wrote:
On 2015-03-12 15:52:02 +0100, Andres Freund wrote:
I guess what you actually intended to test was StandbyModeRequested?
Err, EnableHotStandby.
Yeah pause does not work currently. This change was made by
On 12/03/15 15:53, Andres Freund wrote:
On 2015-03-12 15:52:02 +0100, Andres Freund wrote:
I guess what you actually intended to test was StandbyModeRequested?
Err, EnableHotStandby.
Yeah pause does not work currently. This change was made by committer
and I think the intended change was
Hi,
Unless I'm missing something recovery_target_action = promote/pause
don't work.
There's the following block of code in readRecoveryCommandFile():
/*
* Override any inconsistent requests. Not that this is a change
* of behaviour in 9.5; prior to this we simply
On 2015-03-12 15:52:02 +0100, Andres Freund wrote:
I guess what you actually intended to test was StandbyModeRequested?
Err, EnableHotStandby.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training Services