Ignore recovery_min_apply_delay until recovery has reached consistent state
authorFujii Masao
Sat, 5 Mar 2016 17:29:04 +0000 (02:29 +0900)
committerFujii Masao
Sat, 5 Mar 2016 17:43:17 +0000 (02:43 +0900)
commitf95f1ce003d1453d78a8dd05577d6c61b251d48d
tree36284f72129c49e7ecc15ca0a619f0dce424478d
parent763b8f5d904517c3dffaaa43331a719c80d6e5b0
Ignore recovery_min_apply_delay until recovery has reached consistent state

Previously recovery_min_apply_delay was applied even before recovery
had reached consistency. This could cause us to wait a long time
unexpectedly for read-only connections to be allowed. It's problematic
because the standby was useless during that wait time.

This patch changes recovery_min_apply_delay so that it's applied once
the database has reached the consistent state. That is, even if the delay
is set, the standby tries to replay WAL records as fast as possible until
it has reached consistency.

Author: Michael Paquier
Reviewed-By: Julien Rouhaud
Reported-By: Greg Clough
Backpatch: 9.4, where recovery_min_apply_delay was added
Bug: #13770
Discussion: http://www.postgresql.org/message-id/20151111155006[email protected]
doc/src/sgml/recovery-config.sgml
src/backend/access/transam/xlog.c