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 1lZxsF-0005JW-5Y for pgsql-bugs@arkaria.postgresql.org; Fri, 23 Apr 2021 15:37:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lZxsD-0005CN-OJ for pgsql-bugs@arkaria.postgresql.org; Fri, 23 Apr 2021 15:37:41 +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 1lZxsD-0005CG-IF for pgsql-bugs@lists.postgresql.org; Fri, 23 Apr 2021 15:37:41 +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 1lZxsA-0006qB-G0 for pgsql-bugs@lists.postgresql.org; Fri, 23 Apr 2021 15:37:40 +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 13NFbZfS1356188; Fri, 23 Apr 2021 11:37:35 -0400 From: Tom Lane To: Bruce Momjian cc: tharakan@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16978: Nested CTEs give ERROR in v13 In-reply-to: <20210423145603.GC7629@momjian.us> References: <16978-813ac0832f35db82@postgresql.org> <1313767.1619186886@sss.pgh.pa.us> <20210423145603.GC7629@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Fri, 23 Apr 2021 10:56:03 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1356186.1619192255.1@sss.pgh.pa.us> Date: Fri, 23 Apr 2021 11:37:35 -0400 Message-ID: <1356187.1619192255@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bruce Momjian writes: > On Fri, Apr 23, 2021 at 10:08:06AM -0400, Tom Lane wrote: >> FWIW, I don't see any error from this, either in HEAD or the >> back branches. > Uh, I don't see the failure in 13 head or master, but I do see it from a > 13.2 tree checkout. I will try to find the post-13.2 commit cause. Oh! [ checks commit log ] I bet it's 80ca8464f. regards, tom lane