Request a Demo
Home   >   mailing lists

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 A067B3A3-1CB8-44CC-A695-C5D4EDDE847A@justatheory.com
Whole thread Raw
In response to Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
Tree view 
On Oct 29, 2025, at 19:52, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I'm asking to remove complexity, not add more.  The buildfarm client
> should not be checking either branch names or git tags to control
> this, when we have a perfectly good convention about the existence
> of .abi-compliance-history to control it.

We can remove the branch check, of course, but then you would have to maintain .abi-compliance-history in master, no?

D

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Use BumpContext contexts for TupleHashTables' tablecxt
Next
From: Arne Roland
Date:
Subject: Re: apply_scanjoin_target_to_paths and partitionwise join