Horton

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

Nathan Bossart <nathandbossart@gmail.com>

View thread View on postgr.es
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-21T17:30:32Z
Lists: pgsql-hackers 
On Mon, Oct 20, 2025 at 11:22:29PM +0200, David E. Wheeler wrote:
> I suggest mentioning that new entries should be at the top, that the list
> should be in reverse chronological order.

I felt that this was already covered in the existing commentary.

> Otherwise this looks great, love seeing it!

Thanks for looking.  Now that we have a new run from baza that appears to
be using the updated baseline, I've committed the remaining patches.

For the rest of the back-branches, I'm considering starting with a baseline
of the latest minor version stamps.  While it would be nice to have a
comprehensive history of the ABI compatibility for each major version,
we've lived this long without it, and I think it's unlikely that we'd act
on any breakages that predate the latest release set.  Thoughts?

-- 
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.