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 1scRUk-007KFd-96 for pgsql-bugs@arkaria.postgresql.org; Fri, 09 Aug 2024 15:25:34 +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 1scRUi-0041WT-1J for pgsql-bugs@arkaria.postgresql.org; Fri, 09 Aug 2024 15:25:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1scRUh-0041WK-Ow for pgsql-bugs@lists.postgresql.org; Fri, 09 Aug 2024 15:25:31 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1scRUf-003u0s-4c for pgsql-bugs@lists.postgresql.org; Fri, 09 Aug 2024 15:25:30 +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 479FPRlv2799440; Fri, 9 Aug 2024 11:25:27 -0400 From: Tom Lane To: Richard Guo cc: vasiliy.boytsov@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for In-reply-to: <2548861.1723174234@sss.pgh.pa.us> References: <18576-9feac34e132fea9e@postgresql.org> <2336091.1723137115@sss.pgh.pa.us> <2493069.1723149304@sss.pgh.pa.us> <2548861.1723174234@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Thu, 08 Aug 2024 23:30:34 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2799438.1723217127.1@sss.pgh.pa.us> Date: Fri, 09 Aug 2024 11:25:27 -0400 Message-ID: <2799439.1723217127@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > Richard Guo writes: >> Agreed. Do you think it would be helpful to add some assertions to >> verify the plan type? > I thought about that but didn't experiment with it. I wonder whether > it'd just make the code more fragile. Still, it might be useful to > verify that things are happening as we expect. After sleeping on it, I elected to add the Asserts as suggested, except in v12 where they'd have had to look different. That's not strictly a matter of laziness: v12's next release will be its last, and I've been burned often enough to become very hesitant about pushing even slightly-questionable code into an EOL release. Pushed with that change. regards, tom lane