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>, pgsql-hackers(at)lists(dot)postgresql(dot)org, bruce(at)momjian(dot)us, andrew(at)dunslane(dot)net, nathandbossart(at)gmail(dot)com
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date: 2025-10-30 17:03:23
Message-ID: 3142CBFD-89C5-4E0E-9B6A-194260E5634D@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

> We can put a note in the compliance check result for new STABLE
> branches - "no .abi-compliance-history file found", but keep the
> client status green?

Yes, I think that’s the thing to do.

D

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-10-30 17:17:03 Re: Remaining dependency on setlocale()
Previous Message Bruce Momjian 2025-10-30 16:59:41 Re: [PING] fallocate() causes btrfs to never compress postgresql files