From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: abi-compliance-checker |
Date: | 2023-05-29 17:01:20 |
Message-ID: | CAH2-WzmvOCbDqkAW9BiYXNXkt9DRbzC2tA+Zv46pXxW2kZWzUA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, May 28, 2023 at 9:34 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I'll try to come up with a standard abi-compliance-checker Postgres
> workflow once I'm back from pgCon.
Ideally, we'd be able to produce reports that cover an entire stable
release branch at once, including details about how things changed
over time. It turns out that there is a tool from the same family of
tools as abi-compliance-checker, that can do just that:
https://github.com/lvc/abi-tracker
There is an abi-tracker example report, here:
https://abi-laboratory.pro/?view=timeline&l=glib
It's exactly the same presentation as the report I posted recently,
once you drill down. That seems ideal.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-05-29 17:49:14 | Re: PG 16 draft release notes ready |
Previous Message | Peter Geoghegan | 2023-05-29 16:55:18 | Re: benchmark results comparing versions 15.2 and 16 |