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

Nathan Bossart <nathandbossart@gmail.com> writes:
> On Fri, Oct 17, 2025 at 01:15:20PM -0400, Tom Lane wrote:
>> FWIW, I favor the approach of having an in-tree, per-branch file
>> containing the commit hash of a commit that is the current ABI
>> reference for that branch.

> I'm new to the topic, but IMHO the per-branch file approach is by far the
> best approach.  Not only is it much more flexible, but we could even use it
> as a centralized list of ABI breaks for a given branch with justification
> for each.  I can't think of any strong advantages of keeping this stuff in
> git metadata.  git itself uses a file for blame.ignoreRevsFile...

Good idea.  We'd have to allow comments in the file, but that's
probably a good thing anyway.

            regards, tom lane