| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, 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 21:45:14 |
| Message-ID: | 20170421214514.gvfur5zapaia6lgf@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2017-04-21 17:04:08 -0400, Tom Lane wrote:
> Some excavation in the buildfarm database says that the coverage for
> the recovery-check test has been mighty darn thin up until just
> recently.
Hm, not good. Just enabled it for most of my animals (there seems to be
no point in having it on the C89 animal). Very curious what it'll do to
skink's runtime :/. I'll add a few more cores to the machine, otherwise
it'll probably wreak havock.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-21 23:48:44 | pgsql: doc: Update link |
| Previous Message | Tom Lane | 2017-04-21 21:04:08 | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-04-21 22:20:54 | Re: scram and \password |
| Previous Message | Tom Lane | 2017-04-21 21:04:08 | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |