Re: ABI Compliance Checker GSoC Project

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: ABI Compliance Checker GSoC Project
Date: 2025-07-13 18:37:27
Message-ID: F1C4A8F2-3F04-4663-8B62-BFDA4417D4F2@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 13, 2025, at 14:34, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com> wrote:

> Here, I had a proposal: In case an ABI break is found, then loop
> through the commits after the last run to find the offending commit.
> We can also give the animal owner the option to decide whether they
> want to use their own machine to perform this search or not. Let me
> know your thoughts on this.

Presumably you could work your way backwards until the ABI break disappears. That should minimize the number of commits you have to compile and test.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mankirat Singh 2025-07-13 18:45:19 Re: ABI Compliance Checker GSoC Project
Previous Message Dmitry Dolgov 2025-07-13 18:37:26 Re: Changing shared_buffers without restart