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 3142CBFD-89C5-4E0E-9B6A-194260E5634D@justatheory.com
Whole thread Raw
In response to Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()  (Mankirat Singh <mankiratsingh1315@gmail.com>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
On Oct 30, 2025, at 11:22, Mankirat Singh <mankiratsingh1315@gmail.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


Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PING] fallocate() causes btrfs to never compress postgresql files
Next
From: Jeff Davis
Date:
Subject: Re: Remaining dependency on setlocale()