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

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date: 2025-10-17 22:51:32
Message-ID: 8BF4CB66-9DD7-41A3-B495-28B13D302F51@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 17, 2025, at 17:51, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-10-17 23:07:36 Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Previous Message Tomas Vondra 2025-10-17 22:49:56 Re: Optimizing ResouceOwner to speed up COPY