Re: recovery_target_time and standby_mode

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: recovery_target_time and standby_mode
Date: 2014-11-06 01:44:45
Message-ID: CAB7nPqSSHONNoH4dyj4f_1roDct9-VemT+Z18JYDZ+MH_sd7LQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 6, 2014 at 10:41 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Thu, Nov 6, 2014 at 10:00 AM, Greg Stark <stark(at)mit(dot)edu> wrote:
>> On Thu, Nov 6, 2014 at 12:32 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>> When the recovery_target_time is reached, switch to streaming
>>> replication and stay a standby.
>>
>> Then shouldn't he just not specify a recovert_target at all? That's
>> the default behaviour for standby_mode on, the whole point of
>> recovery_target is to specify when to stop recovery and leave standby
>> mode, no?
> Agreed with Greg, once a target recovery is switched the node gets out
> of recovery. What the user should have done here is not specify
> recovery_target_time in the standby's recovery.conf such as it follows
> the master through streaming.
Just adding: ... On the new timeline that master is bumping to. If the
standby already replayed of the point where WAL forked on master, then
the standby should be rewinded.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2014-11-06 02:15:17 Re: recovery_target_time and standby_mode
Previous Message Michael Paquier 2014-11-06 01:41:43 Re: recovery_target_time and standby_mode