Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h4RX3-0003kX-CW for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Mar 2019 14:40:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h4RX1-0006t0-Sn for pgsql-bugs@arkaria.postgresql.org; Thu, 14 Mar 2019 14:40:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h4RX1-0006st-Mc for pgsql-bugs@lists.postgresql.org; Thu, 14 Mar 2019 14:40:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h4RWz-0001vL-4H for pgsql-bugs@lists.postgresql.org; Thu, 14 Mar 2019 14:40:27 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x2EEeKNG003813; Thu, 14 Mar 2019 10:40:20 -0400 From: Tom Lane To: exclusion@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15694: Server crash in EXPLAIN with LATERAL and a partitioned table In-reply-to: <15694-74f2ca97e7044f7f@postgresql.org> References: <15694-74f2ca97e7044f7f@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 14 Mar 2019 11:24:27 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3811.1552574420.1@sss.pgh.pa.us> Date: Thu, 14 Mar 2019 10:40:20 -0400 Message-ID: <3812.1552574420@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > CREATE TABLE prt1_l (a int) PARTITION BY RANGE(a); > CREATE TABLE prt2_l (a int); > EXPLAIN > SELECT * FROM prt1_l t1 LEFT JOIN LATERAL > (SELECT t1.a as t1a, prt1_l.a FROM prt1_l) t2 ON t1.a = t2.a; > crashes the server with the stack trace: Huh. Clearly, when we added that Assert, we should've fixed set_dummy_rel_pathlist so that it would properly populate the required_outer of the dummy path. I'm surprised though that this wasn't already exposed by the existing regression tests... regards, tom lane