| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Improve replication lag interpolation after idle period |
| Date: | 2017-06-23 18:06:19 |
| Message-ID: | E1dOSyJ-0007Cs-IZ@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Improve replication lag interpolation after idle period
After sitting idle and fully replayed for a while and then encountering
a new burst of WAL activity, we interpolate between an ancient sample and the
not-yet-reached one for the new traffic. That produced a corner case report
of lag after receiving first new reply from standby, which might sometimes
be a large spike.
Correct this by resetting last_read time and handle that new case.
Author: Thomas Munro
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/9ea3c64124af039219aa5030d7af675dce5daa60
Modified Files
--------------
src/backend/replication/walsender.c | 29 +++++++++++++++++++++++++----
1 file changed, 25 insertions(+), 4 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-06-23 18:20:07 | pgsql: Rethink behavior of pg_import_system_collations(). |
| Previous Message | Simon Riggs | 2017-06-23 17:17:37 | pgsql: Minor corrections to high availability docs |