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

From David E. Wheeler
Subject Re: ABI Compliance Checker GSoC Project
Date
Msg-id D093515C-07AF-43AB-B37D-AD4E118D796C@justatheory.com
Whole thread Raw
In response to Re: ABI Compliance Checker GSoC Project  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sep 12, 2025, at 13:53, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> That seems substantially more complicated than just moving which
> commit is considered the baseline.  It might be less reliable too:
> if the exclusions are written sloppily, they might hide problems
> we'd rather find out about.  (I do not regard valgrind suppression
> files as a model of good engineering...)

It would certainly be easier to start with some marker for the baseline commit. We an always add some more complicated
stuffin the future if it turns out to be desirable. I know there’s some stuff built in to Abigail for that. But IMHO it
makessense to start with the simplest solution and see whether anything else is needed later. 

D
Attachment

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: We broke the defense against accessing other sessions' temp tables
Next
From: Jim Jones
Date:
Subject: Re: Add notification on BEGIN ATOMIC SQL functions using temp relations