Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting
Date
Msg-id CA+TgmobuFRFX+V-7ZChRACRFGcK4Ht6H6ZxMEauVisxKUA_-mA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting  (Piotr Stefaniak <postgres@piotr-stefaniak.me>)
Responses Re: [HACKERS] recovery_target_time = 'now' is not an error but stillimpractical setting  (Piotr Stefaniak <postgres@piotr-stefaniak.me>)
List pgsql-hackers
Tree view 
On Fri, Aug 18, 2017 at 4:39 AM, Piotr Stefaniak
<postgres@piotr-stefaniak.me> wrote:
> 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".

Can you use recovery_target_action='shutdown' instead?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
Next
From: David Steele
Date:
Subject: Re: [HACKERS] Update low-level backup documentation to match actual behavior