| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: standby apply lag on inactive servers |
| Date: | 2020-01-29 13:48:37 |
| Message-ID: | 20200129134837.GA29972@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Jan-29, Kyotaro Horiguchi wrote:
> But as more significant issue, nowadays PostgreSQL doesn't run a
> checkpoint if it is really inactive (that is, if no "important" WAL
> records have issued.).
Yeah, I mentioned this in message
<20200127203419(dot)GA15216(at)alvherre(dot)pgsql>. The solution for monitoring
purposes is to use the new "lag" columns in pg_stat_replication. But
that's not available in older releases (prior to 10), so this change is
still useful.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2020-01-29 13:50:11 | Re: [HACKERS] Block level parallel vacuum |
| Previous Message | Robert Haas | 2020-01-29 13:48:26 | Re: [Proposal] Global temporary tables |