Re: [HACKERS] Fast promotion not used when doing a recovery_targetPITR restore? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Fast promotion not used when doing a recovery_targetPITR restore?
Date
Msg-id CAB7nPqREKUQFt++MbWzwtzedKxRnN7ZhOL1QAuXOtKLssN_8eg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Fast promotion not used when doing a recovery_targetPITR restore?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Wed, Jun 28, 2017 at 6:13 AM, Andres Freund <andres@anarazel.de> wrote:
> You seem to completely argue besides my point that the replication path
> is *more* robust by now?  And there's plenty scenarios where a faster
> startup is quite crucial for performance. The difference between an
> immediate shutdown + recovery without checkpoint to a fast shutdown can
> be very large, and that matters a lot for faster postgres updates etc.

If you go that way, it seems safer to me if users had some control
with a switch, defaulting to the previous behavior. And a complete
switch to the newer behavior could be done later on depending on what
has been found.
-- 
Michael



pgsql-hackers by date:

Previous
From: Mark Rofail
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Race conditions with WAL sender PID lookups