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 1qrqTG-00602s-Jw for pgsql-committers@arkaria.postgresql.org; Sun, 15 Oct 2023 02:03:10 +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 1qrqTD-009n6r-8X for pgsql-committers@arkaria.postgresql.org; Sun, 15 Oct 2023 02:03:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qrqTD-009n6j-17 for pgsql-committers@lists.postgresql.org; Sun, 15 Oct 2023 02:03:07 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qrqT4-000ipo-SQ for pgsql-committers@lists.postgresql.org; Sun, 15 Oct 2023 02:03:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 39F22toL1991712; Sat, 14 Oct 2023 22:02:55 -0400 From: Tom Lane To: Noah Misch cc: Peter Geoghegan , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic In-reply-to: <20231015013607.61@rfd.leadboat.com> References: <1974777.1697327121@sss.pgh.pa.us> <20231015000358.2d@rfd.leadboat.com> <1980111.1697329678@sss.pgh.pa.us> <20231015013607.61@rfd.leadboat.com> Comments: In-reply-to Noah Misch message dated "Sat, 14 Oct 2023 18:36:07 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1991710.1697335375.1@sss.pgh.pa.us> Date: Sat, 14 Oct 2023 22:02:55 -0400 Message-ID: <1991711.1697335375@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Noah Misch writes: > On Sat, Oct 14, 2023 at 08:27:58PM -0400, Tom Lane wrote: >> Well, that's indeed going to be a pain for affected people, but >> it doesn't seem like a reason to also break installcheck. > That's right. We don't have a standard that installcheck of v13.N will have > zero diffs on an initdb from v13.0. Um ... don't we? I do not recall very many cases where we changed initial catalog contents at all in a point release, and I don't think any of those cases intentionally created regression diffs. > We've got bigger fish to fry. True, this isn't going to affect many people either way. But I don't think you've made a good precedent here. regards, tom lane