| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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-19 09:42:36 |
| Message-ID: | 8b203d4c-11be-4923-9c98-3973e4d65f24@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18.06.24 00:40, David E. Wheeler wrote:
> 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.
The above thread contains a lengthy discussion about what one could do.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2024-06-19 10:36:51 | Re: Add 64-bit XIDs into PostgreSQL 15 |
| Previous Message | Peter Eisentraut | 2024-06-19 09:41:04 | Re: Proposal: Document ABI Compatibility |