Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting - Mailing list pgsql-hackers

From Piotr Stefaniak
Subject Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting
Date
Msg-id DBXPR03MB365B3EEAC1941BD42E9FF91F2800@DBXPR03MB365.eurprd03.prod.outlook.com
Whole thread Raw
In response to Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
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".

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting
Next
From: Ildar Musin
Date:
Subject: [HACKERS] Proposal: global index