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 1mQWq5-0001j9-FJ for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Sep 2021 15:28:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mQWq4-0001hu-Fe for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Sep 2021 15:28:44 +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 1mQWq4-0001hm-8P for pgsql-hackers@lists.postgresql.org; Wed, 15 Sep 2021 15:28:44 +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 1mQWpy-0001XZ-1Y for pgsql-hackers@postgresql.org; Wed, 15 Sep 2021 15:28:43 +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 18FFSSvf984395; Wed, 15 Sep 2021 11:28:28 -0400 From: Tom Lane To: Andrew Dunstan cc: torikoshia , Peter Eisentraut , Pgsql Hackers Subject: Re: EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails In-reply-to: <24ce73f9-c714-9a7c-6cc0-34e724c8f1c9@dunslane.net> References: <5bafa66ad529e11860339565c9e7c166@oss.nttdata.com> <3208199.1631039493@sss.pgh.pa.us> <24ce73f9-c714-9a7c-6cc0-34e724c8f1c9@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Wed, 15 Sep 2021 11:05:02 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <984393.1631719708.1@sss.pgh.pa.us> Date: Wed, 15 Sep 2021 11:28:28 -0400 Message-ID: <984394.1631719708@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On 9/10/21 10:10 AM, torikoshia wrote: >> I've attached the patch for the changes made for this test for your >> reference, but I'm not sure it's appropriate for creating a new >> CoercionForm to fix the issue.. > This is listed as an open item for release 14. Is it planned to commit > the patch? If not, we should close the item. I do not think that patch is a proper solution, but we do need to do something about this. regards, tom lane