| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: abi-compliance-checker |
| Date: | 2025-01-18 16:47:19 |
| Message-ID: | B142EE8A-5D38-48B9-A4BB-82D69A854B55@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings old thread.
On Mar 4, 2024, at 07:50, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> Maybe the way forward here is to write a buildfarm module for this, and then see from there what further needs there are.
Given the PostgreSQL 17.1 kerfuffle and the addition of API and API guidance to the docs (discussion thread[1]), I’ve started a Google Summer of Code proposal[2] to take the example Peter G posted here and work up a solution that publishes a report and sends notifications for each push to a back branch. I put myself down as a mentor, but perhaps one of you who has thought about this problem and experimented with solutions might be a better choice, or at least co-mentor. If so, please add your name to the proposal. Oh, and of course, please make any corrections you deem fit.
Best,
David
[1]: https://postgr.es/m/5DA9F9D2-B8B2-43DE-BD4D-53A4160F6E8D@justatheory.com
[2]: https://wiki.postgresql.org/wiki/GSoC_2025#ABI_Compliance_Checker
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2025-01-18 16:51:08 | Re: Confine vacuum skip logic to lazy_scan_skip |
| Previous Message | Andrey M. Borodin | 2025-01-18 16:31:12 | Re: Timeline issue if StartupXLOG() is interrupted right before end-of-recovery record is done |