Re: ABI Compliance Checker GSoC Project - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: ABI Compliance Checker GSoC Project
Date
Msg-id 202506031812.i3b6asrafsm6@alvherre.pgsql
Whole thread Raw
In response to Re: ABI Compliance Checker GSoC Project  (Mankirat Singh <mankiratsingh1315@gmail.com>)
List pgsql-hackers
On 2025-Jun-03, Mankirat Singh wrote:

> On Tue, 3 Jun 2025 at 20:49, Álvaro Herrera <alvherre@kurilemu.de> wrote:

> > Please elaborate.  Can you not write a suppression file that says
> > "ignore offset changes for ios_in_progress in ReadStream", for example?
> 
> I can do that, and that's what's causing the problem. According to
> the documentation for these suppression files[1], we have to mention
> the particular symbol name we need to suppress like "ReadStream" or
> something particular like "ignore offset changes for ios_in_progress
> in ReadStream between member1 and member 2" which is humanly very hard
> to do as for sure there will be 100s of symbols in postgres like this
> which needs to be ignored in that case.

Well, now that I grep the source for ReadStream, I realize that the
struct is defined in a .c file, not in any .h files, so you're right
that the tooling needs a way to understand that changes to this symbol
must not raise any alarms; and that way must not involve a manually
written suppression file.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
Officer Krupke, what are we to do?
Gee, officer Krupke, Krup you! (West Side Story, "Gee, Officer Krupke")



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Correcting freeze conflict horizon calculation
Next
From: Andres Freund
Date:
Subject: Re: autoprewarm_dump_now