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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
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 21:51:44
Message-ID: 1841741.1760737904@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David E. Wheeler" <david(at)justatheory(dot)com> writes:
> 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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-10-17 22:02:16 Re: Change initdb default to the builtin collation provider
Previous Message David E. Wheeler 2025-10-17 21:41:27 Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()