Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vEDey-007gDD-7e for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Oct 2025 21:24:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vEDev-003mQg-90 for pgsql-hackers@arkaria.postgresql.org; Wed, 29 Oct 2025 21:24:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vEDeu-003mQY-Vb for pgsql-hackers@lists.postgresql.org; Wed, 29 Oct 2025 21:24:44 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vEDer-004S40-33 for pgsql-hackers@postgresql.org; Wed, 29 Oct 2025 21:24:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=UfSf5rXYXZ6xq6KLEyQkQwaGUkgWDMxsCHgRgwSifN0=; b=BvQAf qrokXXvqchKcwI+1phIz2L/UFYnYojUrnFoqmSJcyiEEaNpRqwxdcjBw88+0kPkdl7TjDnClC4rEq d+SEC4dQ4gPC2AWOPPUiaj1W/V1sajmwDj1sJ17KX+edtvfh9eGSqKppTb+NmbfCLYY3gpQJMkkG3 5Dh8Gc1ZD++A8/a36MQSJvkCUc+hS5VYuTbQcZF2qMo5mbMks3OHaRCqi+IlVCx92vZd16ap3OdBx IV/oFqeelkUUQjz/X7g9MlmuXfjnkUnE5XCWvZP1e9utCuWwDLwgeAl9M4OmfwFsmehTqbdSNX0eA nKabUs062STSpiGePAcbZ70IUXv/A==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1vEDep-00000000f2d-3vX7; Wed, 29 Oct 2025 17:24:39 -0400 Date: Wed, 29 Oct 2025 17:24:39 -0400 From: Bruce Momjian To: Tom Lane Cc: "David E. Wheeler" , Nathan Bossart , pgsql-hackers@postgresql.org, Andrew Dunstan , Mankirat Singh Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats() Message-ID: References: <1841741.1760737904@sss.pgh.pa.us> <8BF4CB66-9DD7-41A3-B495-28B13D302F51@justatheory.com> <1851362.1760742456@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1851362.1760742456@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Oct 17, 2025 at 07:07:36PM -0400, Tom Lane wrote: > "David E. Wheeler" writes: > > On Oct 17, 2025, at 17:51, Tom Lane wrote: > >> NO. The rule is: if there's no such file, do not apply ABI checking. > >> We are not interested in ABI complaints against master. > > > It only runs against maintenance branches. > > That seems overcomplicated: how does the buildfarm know > what's a maintenance branch? I think the rule should be > just "run ABI checks if the control file exists, else not". > > As an example of why that's better, what if we did decide > we wanted ABI checks on master? I assume we would want ABI breakage checks on master between Beta 1 and the time we branch for the new major release in July. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.