| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: differential code coverage |
| Date: | 2023-04-05 09:00:39 |
| Message-ID: | 8DD79CE2-DBCD-4E9F-A8A4-9F26832ED889@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 4 Apr 2023, at 18:03, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm planning to generate the 15->16 differential code coverage, once the
> feature freeze has been reached.
Cool!
> I think for now it'd likely be a small script that'd generate the code
> coverage across versions. Do we want to have that in the source tree?
If it's published on pg.o like discussed below then I think it makes sense to
include it.
> Is there any interest in a) using the hierarchical output b) differential
> output on coverage.pg.o?
I would like to see that. If there are concerns about replacing the current
coverage report with one from an unreleased (and potentially buggy) lcov, we
could perhaps use diff.coverage.pg.o until it's released?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Drouvot, Bertrand | 2023-04-05 09:11:38 | Re: Minimal logical decoding on standbys |
| Previous Message | Daniel Gustafsson | 2023-04-05 08:57:18 | Re: GUC for temporarily disabling event triggers |