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

From David E. Wheeler
Subject Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date
Msg-id 8BF4CB66-9DD7-41A3-B495-28B13D302F51@justatheory.com
Whole thread Raw
In response to Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
On Oct 17, 2025, at 17:51, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>> 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
>
> NO.  The rule is: if there's no such file, do not apply ABI checking.
> We are not interested in ABI complaints against master.

It only runs against maintenance branches.

D





pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Optimizing ResouceOwner to speed up COPY
Next
From: Tom Lane
Date:
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()