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: Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, nathandbossart(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-19 20:37:42
Message-ID: F6567E02-23FD-455C-95D2-5CB076BC4E65@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 18, 2025, at 22:48, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com> wrote:

> I've implemented the support for .abi-compliance-history file. If the file is present in a STABLE branch, it will be used by default; otherwise, the latest tag will be used. You can view the changes here[1].

I’ve now deployed this change (well, a subsequent change that does it better) to baza, so once the .abi-compliance-history has been committed to the rev 18 branch (assuming the format is compatible), it should start passing again.

Best,

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2025-10-19 22:06:45 Re: Optimize LISTEN/NOTIFY
Previous Message Philip Alger 2025-10-19 19:30:04 Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement