Re: recovery_target_time = 'now' is not an error but still impractical setting

From: Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: recovery_target_time = 'now' is not an error but still impractical setting
Date: 2017-08-18 08:39:10
Message-ID: DBXPR03MB365B3EEAC1941BD42E9FF91F2800@DBXPR03MB365.eurprd03.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017-08-17 11:24, Simon Riggs wrote:
> Your suggestion of "furthest" is already the default behaviour.
>
> Why are you using 'now'? Why would you want to pick a randomly
> selected end time?

The idea in both cases was to stop the recovery in order to prevent the
standby from selecting new timeline. I want to be able to continue the
recovery from future WAL files. "Furthest" really meant "as far as
possible without completing recovery".

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ildar Musin 2017-08-18 09:12:58 Proposal: global index
Previous Message Simon Riggs 2017-08-18 08:21:47 Re: recovery_target_time = 'now' is not an error but still impractical setting