Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kPU7B-0004gT-11 for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Oct 2020 17:17:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kPU7A-00083w-0e for pgsql-hackers@arkaria.postgresql.org; Mon, 05 Oct 2020 17:17:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kPU79-00083S-Pi for pgsql-hackers@lists.postgresql.org; Mon, 05 Oct 2020 17:17:31 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kPU77-0006U1-Qd for pgsql-hackers@lists.postgresql.org; Mon, 05 Oct 2020 17:17:31 +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 095HHRUx1786356; Mon, 5 Oct 2020 13:17:27 -0400 From: Tom Lane To: David Rowley cc: PostgreSQL Developers Subject: Re: Buglets in equivclass.c In-reply-to: References: <1508010.1601832581@sss.pgh.pa.us> Comments: In-reply-to David Rowley message dated "Mon, 05 Oct 2020 10:11:04 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1786354.1601918247.1@sss.pgh.pa.us> Date: Mon, 05 Oct 2020 13:17:27 -0400 Message-ID: <1786355.1601918247@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk David Rowley writes: > On Mon, 5 Oct 2020 at 06:29, Tom Lane wrote: >> I'm unsure whether to back-patch either of these. They both seem to be >> just latent bugs so far as the core code is concerned, but the first one >> in particular seems like something that could bite extension code. >> Thoughts? > That's a good question. I'm leaning towards backpatching both of them. > The 2nd is new as of v13, so it does not seem unreasonable that > someone has just not yet stumbled on it with some extension that adds > extra child ECs. I can imagine a use case for that, by getting rid of > needless equality quals that duplicate the partition constraint. The > fix for the first just seems neater/faster/correct, so I can't really > see any reason not to backpatch it. Yeah, that's my conclusion too after sleeping on it. Pushed, thanks for reviewing. regards, tom lane