On Fri, Aug 18, 2017 at 4:39 AM, Piotr Stefaniak <postg...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
