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

From Tom Lane
Subject Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date
Msg-id 2923669.1761781931@sss.pgh.pa.us
Whole thread Raw
In response to Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
"David E. Wheeler" <david@justatheory.com> writes:
> On Oct 29, 2025, at 17:37, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> ... I still do not like having any
>> policy decisions about which branches to check hard-wired into the
>> buildfarm client.

> Well that’s pretty easily addressed by adding a configuration for it. Maybe a regex to match branches, defaulting to
itscurrent value[0], `/_STABLE$/`. 

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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Fix bogus use of "long" in aset.c
Next
From: Tom Lane
Date:
Subject: Re: Fix bogus use of "long" in aset.c