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 1sg5vP-00FHOp-P9 for pgsql-bugs@arkaria.postgresql.org; Mon, 19 Aug 2024 17:12:11 +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 1sg5uP-000h7g-41 for pgsql-bugs@arkaria.postgresql.org; Mon, 19 Aug 2024 17:11:09 +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 1sg5uO-000h70-RJ for pgsql-bugs@lists.postgresql.org; Mon, 19 Aug 2024 17:11:09 +0000 Received: from mail-wr1-x42d.google.com ([2a00:1450:4864:20::42d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sg5uJ-000REq-Ly for pgsql-bugs@lists.postgresql.org; Mon, 19 Aug 2024 17:11:08 +0000 Received: by mail-wr1-x42d.google.com with SMTP id ffacd0b85a97d-37198a6da58so2451814f8f.0 for ; Mon, 19 Aug 2024 10:11:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724087462; x=1724692262; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=hbsuZ9M3i+Vp4+5oFbKla3giafnAT5CEOifJwrLDC8M=; b=d6EFJF+PbBEyehhjBLafzuhS/FDHOGITGLUJxoFXxh2lfi8Ji7CP3C+O6zhbdYGCZr jUOdlG+vNhz3rBhx7RoceSWs95wvIhgKchFKWRN++2LCzIFbxSAT7xUDAra5PoYLJyDi vio/50DvbELlE2bE4ljzDvUxBiKahseGrdysD5f2mGlQ8+hRsZTsO6skD6I9J27iM9YY DEIYVlJjV38LqQW+yGnF7PsV3Mtw11h9/CWxeDirfSyOhKz/y4bYaLE2y208sFe4GxL7 Nul4trleqaWPaaznKICZAiMAkYX4ElAZHQXpP3EoBkMTHCTwwMhQRs/lNlakZEAFHjY2 Xc9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724087462; x=1724692262; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=hbsuZ9M3i+Vp4+5oFbKla3giafnAT5CEOifJwrLDC8M=; b=Cn1a7veCWjOX9WdPIukBEAsLvjQTTTbHJjyG8uSqqG3KOzNt8PF9/N6trRgLJFREi6 /vjSSP5LAheZB5yDD4AmedETnWD/OKw6QlEhxzHeoHHXGITGeP0/E8FbnS2jYW1eE3L+ /6kerROyCb2pyhLTnze65Hv5LH66wl7t/OAM9imqzupzOiLf/du8mlJNEDw4Cn12RENd pXquxjFTFkEak9IEk6hfuxkY+erNgLIfSJ0IQVjqIVatFHgUdzhWd1La4TQ42KO8FxDu EvNR4jZxEFmqVKvTRk9tiiBi7uS9FQ+LFPclRa1KmQrQ7+OBSjDi9O3kfZwl1jRQK5jc eq0A== X-Forwarded-Encrypted: i=1; AJvYcCVGWM7Q+UhABsCgbDaoAJgc5PDgsJF7FeCcvz6Ffns/pKl0n95KHNILSn50m9HddUcR2gpn6vFK/D6zlPsYASp/X3we4Kp3uTBYYEsbeQKw X-Gm-Message-State: AOJu0Yw5eh4DHxDXGtrg804YFD57YWdKls/akieVNW9funJugJp8AYcF MktK74Hd5z4DUv8dD663tDvz1uGb3FGBZr/7/vVMI2f3N91JL04y X-Google-Smtp-Source: AGHT+IETxsKzM9icg1Cr1YbpMJnvfQTkL6rd7Fg5TLFTa8vn4q8tUud6Nv01hwgf+VFCRKJe8SqVIw== X-Received: by 2002:adf:e443:0:b0:371:8b49:f49c with SMTP id ffacd0b85a97d-3719431576amr8291030f8f.5.1724087461816; Mon, 19 Aug 2024 10:11:01 -0700 (PDT) Received: from ?IPV6:2a0c:5a83:4c09:9d00:ed42:c0b8:e522:cb22? ([2a0c:5a83:4c09:9d00:ed42:c0b8:e522:cb22]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-3718983a31csm11030080f8f.17.2024.08.19.10.11.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 19 Aug 2024 10:11:01 -0700 (PDT) Message-ID: <5e129a8e-5b8d-4a61-9776-59be99a2c14f@gmail.com> Date: Mon, 19 Aug 2024 19:11:00 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for To: Tom Lane Cc: Richard Guo , pgsql-bugs@lists.postgresql.org References: <18576-9feac34e132fea9e@postgresql.org> <2336091.1723137115@sss.pgh.pa.us> <2493069.1723149304@sss.pgh.pa.us> <2548861.1723174234@sss.pgh.pa.us> <2799439.1723217127@sss.pgh.pa.us> <332f0e30-f90a-4e47-b668-b53f649c244f@gmail.com> <1385302.1724085401@sss.pgh.pa.us> Content-Language: en-US From: Andrei Lepikhov In-Reply-To: <1385302.1724085401@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 19/8/2024 18:36, Tom Lane wrote: > Andrei Lepikhov writes: >> Thanks for pushing this! > >> But could you change this code a little bit? >> I reported this issue a year ago. At that time, it was triggered by the >> CustomScan node [1]. I haven't found the solution there [2]. Your code >> looks like a good tradeoff, and if you slightly change the code (like in >> the attachment), it allows CustomScan to survive such cases. > > This seems like it's making assumptions it shouldn't about what > CustomScan does. If there's an argument for doing this, it should > be added to the adjacent comments. Hm, I got into this problem many times using CustomScan node. Do you have some objections to not allow CustomScan node have a RECORD Var in the target list? For example, once I got this bug designing CustomScan which gathered lightweight statistics on-the-fly under a Sort and GROUP-BY nodes. I didn't change any tuple and had the same target list as the child node. Why we should analyse target list and don't use CustomScan if it contains Var of specific type? > > (Also, what's with the random change in contrib/Makefile?) Oops, it's a waste code, pardon. -- regards, Andrei Lepikhov