Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
David E. Wheeler <david@justatheory.com>
From: "David E. Wheeler" <david@justatheory.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Nathan Bossart <nathandbossart@gmail.com>,
pgsql-hackers@postgresql.org,
Andrew Dunstan <andrew@dunslane.net>,
Mankirat Singh <mankiratsingh1315@gmail.com>
Date: 2025-10-17T21:41:27Z
Lists: pgsql-hackers
On Oct 17, 2025, at 16:19, Tom Lane <tgl@sss.pgh.pa.us> wrote: > I agree. I don't think the buildfarm should consider git tags at all > in this behavior. One reason is that our release process dictates > applying tags at very specific times that aren't necessarily relevant > to deciding that an ABI break is or is not okay. I think we want > moving the baseline to be a considered reaction to an observed ABI > report, and not an action that is automatic according to some other > process. Okay, so the rule is: * If there is no .abi-compliance-history file, baseline from the latest tag * Otherwise, baseline from the first SHA to appear in the file Easy peasy. D