From: Tom Lane <tgl@sss.pgh.pa.us>
To: David E. Wheeler <david@justatheory.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers@postgresql.org, Andrew Dunstan <andrew@dunslane.net>
Cc: Mankirat Singh <mankiratsingh1315@gmail.com>
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date: Wed, 29 Oct 2025 19:52:11 -0400
Message-ID: <2923669.1761781931@sss.pgh.pa.us> (raw)
In-Reply-To: <3476556C-48A4-4ABF-A8F6-186EACA32BE8@justatheory.com>
References: <1841741.1760737904@sss.pgh.pa.us>
<8BF4CB66-9DD7-41A3-B495-28B13D302F51@justatheory.com>
<1851362.1760742456@sss.pgh.pa.us>
<aQKGF1OnClNRY4j4@momjian.us>
<2909069.1761773856@sss.pgh.pa.us>
<3476556C-48A4-4ABF-A8F6-186EACA32BE8@justatheory.com>
"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 its current 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, david@justatheory.com, bruce@momjian.us, nathandbossart@gmail.com, andrew@dunslane.net, mankiratsingh1315@gmail.com
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
In-Reply-To: <2923669.1761781931@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox