回复: Differential Code Coverage report for Postgres - Mailing list pgsql-hackers

From Oreo Yang
Subject 回复: Differential Code Coverage report for Postgres
Date
Msg-id TY4P286MB7376DD8B50845AC54AA5DF35E703A@TY4P286MB7376.JPNP286.PROD.OUTLOOK.COM
Whole thread Raw
In response to Differential Code Coverage report for Postgres  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: Differential Code Coverage report for Postgres
List pgsql-hackers
It looks very cool.
So our goal over 90%?

Thanks,
OreoYang

发件人: Nazir Bilal Yavuz <byavuz81@gmail.com>
已发送: 2025 年 9 月 5 日 星期五 15:09
收件人: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
抄送: Andres Freund <andres@anarazel.de>; Álvaro Herrera <alvherre@kurilemu.de>
主题: Differential Code Coverage report for Postgres

Hi,

I have been working on generating differential code coverage for
Postgres and was able to do so with this script [1]. The script checks
out HEAD and the latest release branch (currently REL_18_STABLE), then
generates a differential coverage report.

I also set up a GitHub Action so the report is updated daily and
published as HTML here [2].

I thought this might be useful to share, and I would be happy to hear
any feedback or suggestions.

CC’ing Álvaro since he had asked about this previously.

[1] https://github.com/nbyavuz/postgres-code-coverage/blob/main/code_coverage.sh
[2] https://nbyavuz.github.io/postgres-code-coverage

--
Regards,
Nazir Bilal Yavuz
Microsoft


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Raw parse tree is not dumped to log
Next
From: Matheus Alcantara
Date:
Subject: Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue