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

From Nathan Bossart
Subject Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date
Msg-id aPfrWJxUIOm1RH5A@nathan
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 Tue, Oct 21, 2025 at 04:13:37PM -0400, Tom Lane wrote:
> I propose that we should make .abi-compliance-history point at these
> commits rather than REL_17_6 et al.  If there is anything later than
> this that affected ABI, it'd be worth finding out I think, even though
> we might choose not to do anything about it.  (In effect, we'd be
> starting the ABI compliance histories there rather than all the way
> back at the .0 releases.)

WFM.  I'll make it so.

I see that baza is currently using the latest tags for <v18.  David, will
it start using the .abi-compliance-history file on the rest of the
back-branches once it is added?

-- 
nathan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Next
From: Arseniy Mukhin
Date:
Subject: Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue