Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats() - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date
Msg-id 17DB0A6A-C967-48A8-B1C0-9A4F31C4F8EF@justatheory.com
Whole thread Raw
In response to Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
On Oct 18, 2025, at 11:14, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I am strongly against relying on suppression files.  I think that
> is a very imprecise technology, and it is certainly harder to use
> than the "choose a blessed reference point" approach.

Seconded. I’m also not keen on using something specific to libabigail if, long term, we want to enable similar checks
onother platforms using other tools that may not support it suppression file format. 

Let’s do the baseline SHA file and see how it goes.

Best,

David
Attachment

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Next
From: Srinath Reddy Sadipiralla
Date:
Subject: Re: Making pg_rewind faster