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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: "David E. Wheeler" <david@justatheory.com>, Mankirat Singh <mankiratsingh1315@gmail.com>, pg@bowt.ie, andrew@dunslane.net, pgsql-hackers@lists.postgresql.org
Date: 2025-10-22T14:40:50Z
Lists: pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes:
> Great.  All back-branches now have an .abi-compliance-history file.

Looks like we're good on v13-v16, but v17 is complaining

1 Removed function:

  [D] 'function bool check_max_slot_wal_keep_size(int*, void**, GucSource)'    {check_max_slot_wal_keep_size}

so I guess we need to add 24f6c1bd4 to that history.

			regards, tom lane



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.