| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Proposal: Document ABI Compatibility |
| Date: | 2024-06-17 22:40:59 |
| Message-ID: | 317E799A-BF30-4C11-B750-F1F163C882B2@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 12, 2024, at 11:57, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> That having been said, it would be useful if there was a community web
> resource for this -- something akin to coverage.postgresql.org, but
> with differential ABI breakage reports. You can see an example report
> here:
>
> https://postgr.es/m/CAH2-Wzm-W6hSn71sUkz0Rem=qDEU7TnFmc7_jG2DjrLFef_WKQ@mail.gmail.com
>
> Theoretically anybody can do this themselves. In practice they don't.
> So something as simple as providing automated reports about ABI
> changes might well move the needle here.
What would be required to make such a thing? Maybe it’d make a good Summer of Code project.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amonson, Paul D | 2024-06-17 22:42:54 | RE: Proposal for Updating CRC32C with AVX-512 Algorithm. |
| Previous Message | David E. Wheeler | 2024-06-17 22:39:07 | Re: Proposal: Document ABI Compatibility |