Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Greg Clough <greg@gclough.com>,
PostgreSQL mailing lists <pgsql-bugs@postgresql.org>,
Simon Riggs <simon@2ndQuadrant.com>
Date: 2015-12-30T14:02:18Z
Lists: pgsql-bugs
On 2015-12-26 22:45:57 +0900, Michael Paquier wrote: > Depending on the use cases, it may be interesting to have a switch > allowing to not apply the delay should a consistent point not be > reached though... Is there actually any case where it's interesting to delay in that scenario? I mean that really can only happen if you changed the configuration to a different delay, or your clock offset changed. Otherwise we should always reach the consistent point before the delay plays a role. I'm tempted to simply only check for delay when consistent.
Commits
-
Ignore recovery_min_apply_delay until recovery has reached consistent state
- a9613ee69246 9.4.7 landed
- f95f1ce003d1 9.5.2 landed
- d34794f7d556 9.6.0 landed