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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>, pg(at)bowt(dot)ie, andrew(at)dunslane(dot)net, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date: 2025-10-21 20:21:44
Message-ID: aPfrWJxUIOm1RH5A@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 21, 2025 at 04:13:37PM -0400, Tom Lane wrote:
> I propose that we should make .abi-compliance-history point at these
> commits rather than REL_17_6 et al. If there is anything later than
> this that affected ABI, it'd be worth finding out I think, even though
> we might choose not to do anything about it. (In effect, we'd be
> starting the ABI compliance histories there rather than all the way
> back at the .0 releases.)

WFM. I'll make it so.

I see that baza is currently using the latest tags for <v18. David, will
it start using the .abi-compliance-history file on the rest of the
back-branches once it is added?

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Arseniy Mukhin 2025-10-21 20:26:55 Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue
Previous Message Tom Lane 2025-10-21 20:13:37 Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()