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: Peter Eisentraut <peter@eisentraut.org>,
"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-31T15:17:11Z
Lists: pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes: > On Fri, Oct 31, 2025 at 12:02:10PM +0100, Peter Eisentraut wrote: >> What is the reason that this file is supposed to contain the history of >> relevant changes, rather than just the last one? >> If you want the history, you could look at the git log of the file itself, >> no? > I think either way would ultimately be fine. I might argue that keeping > the full history in a file with detailed explanations is more accessible > than requiring folks to run > git log .abi-compliance-history > (Plus, if someone doesn't bother to put details in the commit message, you > then have to sleuth further to figure out what changed.) Yeah, that last. I would expect the annotation text in .abi-compliance-history to be specific about the nature of the ABI break, whereas the log message for the commit that changed things might not bother with such details. As we move along with this effort, we might ultimately decide that this scheme is overdoing the amount of detail recorded. But to start with, I'd rather err on the side of recording more info not less. regards, tom lane
Commits
-
Add commit 24f6c1bd4 to v17 .abi-compliance-history.
- 5c659da980e1 17.7 landed
-
Add .abi-compliance-history to back-branches.
- eaf73340cd46 16.11 landed
- d9c5e7129d2b 15.15 landed
- a91f2d822522 17.7 landed
- 7d47278933f4 13.23 landed
- 58ba7e5ebfdf 14.20 landed
-
Add reminder to create .abi-compliance-history.
- b97d8d843a2d 19 (unreleased) landed
-
Update .abi-compliance-history file.
- 93fb76ca4e69 18.1 landed
-
Add .abi-compliance-history to v18 branch.
- a72f7d97bea9 18.1 landed
-
Fix thinko in commit 7d129ba54.
- 399a9e04e549 18.1 cited
-
Fix lookups in pg_{clear,restore}_{attribute,relation}_stats().
- c8af5019bee5 18.1 cited
- 688dc6299a5b 19 (unreleased) cited
-
Add defenses against unexpected changes in the NodeTag enum list.
- eea9fa9b250f 16.0 cited