Replica with large recovery_min_apply_delay is not receiving changes from master after restart until this delay is expired

Edit
Title Replica with large recovery_min_apply_delay is not receiving changes from master after restart until this delay is expired
Topic Bug Fixes
Created 2019-02-12 16:51:00
Last modified 2019-02-12 16:51:58 (1 month, 1 week ago)
Latest email 2019-01-30 14:32:28 (1 month, 3 weeks ago)
Status
2019-03: Needs review
Target version
Authors Konstantin Knizhnik (knizhnik)
Reviewers Martín Marqués (mmarques)Become reviewer
Committer
Links
Emails
Replication & recovery_min_apply_delay
First at 2019-01-30 12:04:53 by Konstantin Knizhnik <k.knizhnik at postgrespro.ru>
Latest at 2019-01-30 14:32:28 by Alvaro Herrera <alvherre at 2ndquadrant.com>
Latest attachment (0001-Support-pg_basebackup-S-in-PostgresNode-backup.patch) at 2019-01-30 14:32:28 from Alvaro Herrera <alvherre at 2ndquadrant.com>
    Attachment (0001-Support-pg_basebackup-S-in-PostgresNode-backup.patch) at 2019-01-30 14:32:28 from Alvaro Herrera <alvherre at 2ndquadrant.com> (Patch: Yes)
    Attachment (wal_apply_delay.patch) at 2019-01-30 12:04:53 from Konstantin Knizhnik <k.knizhnik at postgrespro.ru> (Patch: Yes)
History
When Who What
2019-02-28 13:45:08 Martín Marqués (mmarques) Added mmarques as reviewer
2019-02-12 16:51:58 Konstantin Knizhnik (knizhnik) Changed authors to Konstantin Knizhnik (knizhnik)
2019-02-12 16:51:00 Konstantin Knizhnik (knizhnik) Attached mail thread b271715f-f945-35b0-d1f5-c9de3e56f65e@postgrespro.ru
2019-02-12 16:51:00 Konstantin Knizhnik (knizhnik) Created patch record
Edit