| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump getBlobs query broken for 7.3 servers |
| Date: | 2016-10-07 17:04:30 |
| Message-ID: | 20161007170430.GA779641@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost wrote:
> What would be really nice would be code coverage information for the
> back-branches also, as that would allow us to figure out what we're
> missing coverage for. I realize that we don't like adding new things to
> back-branches as those changes could impact packagers, but that might
> not impact them since that only runs when you run 'make coverage'.
Hmm? 9.1 already has "make coverage", so there's nothing to backpatch.
Do you mean to backpatch that infrastructure even further back than
that?
Or perhaps you are saying that coverage.pg.org should report results for
each branch separately? We could do that ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-10-07 17:12:14 | Re: pg_dump getBlobs query broken for 7.3 servers |
| Previous Message | Stephen Frost | 2016-10-07 16:54:36 | Re: pg_dump getBlobs query broken for 7.3 servers |