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

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>
To: "David E. Wheeler" <david@justatheory.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Mankirat Singh <mankiratsingh1315@gmail.com>, pg@bowt.ie, andrew@dunslane.net, pgsql-hackers@lists.postgresql.org
Date: 2025-10-21T21:44:32Z
Lists: pgsql-hackers
On Tue, Oct 21, 2025 at 10:44:19PM +0200, David E. Wheeler wrote:
> On Oct 21, 2025, at 22:21, Nathan Bossart <nathandbossart@gmail.com> wrote:
>> 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?
> 
> It should, yes. I added the latest changes from Mankirat to add support
> for it.

Great.  All back-branches now have an .abi-compliance-history file.

-- 
nathan



Commits

  1. Add commit 24f6c1bd4 to v17 .abi-compliance-history.

  2. Add .abi-compliance-history to back-branches.

  3. Add reminder to create .abi-compliance-history.

  4. Update .abi-compliance-history file.

  5. Add .abi-compliance-history to v18 branch.

  6. Fix thinko in commit 7d129ba54.

  7. Fix lookups in pg_{clear,restore}_{attribute,relation}_stats().

  8. Add defenses against unexpected changes in the NodeTag enum list.