| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |
| Date: | 2017-04-21 19:06:29 |
| Message-ID: | 20170421190629.3srqyohjocgdvhhr@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Simon Riggs wrote:
> Replication lag tracking for walsenders
>
> Adds write_lag, flush_lag and replay_lag cols to pg_stat_replication.
Did anyone notice that this seems to be causing buildfarm member 'tern'
to fail the recovery check? See here:
https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=tern&dt=2017-04-21%2012%3A48%3A09&stg=recovery-check
which has
TRAP: FailedAssertion("!(lsn >= prev.lsn)", File: "walsender.c", Line: 3331)
Line 3331 was added by this commit.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-21 19:33:38 | pgsql: doc: Fix typo |
| Previous Message | Tom Lane | 2017-04-21 18:48:35 | pgsql: Remove long-obsolete catering for platforms without F_SETFD/FD_C |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2017-04-21 19:26:17 | Re: some review comments on logical rep code |
| Previous Message | Tom Lane | 2017-04-21 18:54:40 | Re: Unportable implementation of background worker start |