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 1sj64h-00EXGv-Cn for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Aug 2024 23:58: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 1sj64f-00EV12-2w for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Aug 2024 23:58: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 1sj64e-00EV0u-N3 for pgsql-hackers@lists.postgresql.org; Tue, 27 Aug 2024 23:58:09 +0000 Received: from mail-lf1-x12d.google.com ([2a00:1450:4864:20::12d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sj64c-001lDW-P3 for pgsql-hackers@lists.postgresql.org; Tue, 27 Aug 2024 23:58:07 +0000 Received: by mail-lf1-x12d.google.com with SMTP id 2adb3069b0e04-53346132348so7274293e87.2 for ; Tue, 27 Aug 2024 16:58:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724803085; x=1725407885; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TpSytfOuWEK8N7WQ1b9uRRk6u1XVdv7QMRkckvrfeh8=; b=RqJvVtreqss+OPXOwBaR4B3cmwdf609sb0EVnXRFe4Zsry771zjS8eAFv4bj8gIA5i u6uNMwrtWmZcgrykfDo31/uP6wlLv5baVoHqzYhBe9Y0MAIGc/sUHxPYtJ5UU2/tphLn 85fTHbjgtC4JqCghgnY79umtlCszTEF3ZPwd1F/OrDi6UnJsL87FFapagnttMoamdwlW 1gDi3RC2fTmC3STccjv/x4+/cNWLiN9PNPHN/HRRWexlkpfp7sF3ruGSaPAKslCzcAsw 6IyVRB1Yh7Syg/owqhXwa4DJcaO/lLnob2VYVb/rGqP3KzoV1p/LvAsIoCveqgtk1BrP qFow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724803085; x=1725407885; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TpSytfOuWEK8N7WQ1b9uRRk6u1XVdv7QMRkckvrfeh8=; b=aqyhFYekYrf4e9aF7cdR6+t7pY3IfhkuneBkgv8v52/3iVyvFjTCxoC0w5GpQDc74y TtXTmT6lxj4TWPguvKkVj/NyWdzDKlOFKazU4UHrf1OpLMyOuCptbqgIt1MK/9uL1UPO rplOleUDBV/X255BTjdBS+umIDZEJrPfO7GCmXYRDEMptH+mEzIIAIp1CzP940SJnR96 cg8XfyF8ITmthn/MplGDJ20eixt+OU75TeQAs7/9SbCm/BVl5bRLXy+AfgAEeeV5vHMP D296B+4OrlH22SHiDCACTtFOOmphcMlcUfEBa5gP0+6pkcKVNBBnDdi8DxOcMx/IETxq wfRw== X-Forwarded-Encrypted: i=1; AJvYcCVWTRdR0A8ygOQ5PtlwBmrjiqm3X5yL7PTU4ijEdMa5klVmBoNs2oYbWGzOfj6SD6HOhRmbtkMUZVbG36EF@lists.postgresql.org X-Gm-Message-State: AOJu0YzN4eZ14baYfhPWNyaYkol61339QwEIMDeXfNFPTr+Cdaetpn+m pAIaJtiPqDCdo0HxQ2lZeFw+qg4k1PsQBsT0bfBuBblu00G98WvoJ2c4OBEMtRdy/BTFYYNpL7+ sGVxcJv749jW6aincJcZmDStqdZA= X-Google-Smtp-Source: AGHT+IEeFooHchi6Ff4o0F8n1jx1jEAfzJubnKjtXZfvCzcU9AZwwA9kVGo6oFLJJbRP1Qi113gn+1KnHq0ALjtutl4= X-Received: by 2002:ac2:4bd1:0:b0:534:543e:1884 with SMTP id 2adb3069b0e04-534543e199amr974906e87.44.1724803084604; Tue, 27 Aug 2024 16:58:04 -0700 (PDT) MIME-Version: 1.0 References: <2962669.1724722813@sss.pgh.pa.us> <2965760.1724724227@sss.pgh.pa.us> <3104695.1724775341@sss.pgh.pa.us> <3147330.1724795532@sss.pgh.pa.us> <3156371.1724800521@sss.pgh.pa.us> <3159017.1724801876@sss.pgh.pa.us> In-Reply-To: <3159017.1724801876@sss.pgh.pa.us> From: David Rowley Date: Wed, 28 Aug 2024 11:57:53 +1200 Message-ID: Subject: Re: Significant Execution Time Difference Between PG13.14 and PG16.4 for Query on information_schema Tables. To: Tom Lane Cc: Richard Guo , nikhil raj , pgsql-hackers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 28 Aug 2024 at 11:37, Tom Lane wrote: > Oh, scratch that, I see you mean this is an additional way to do it > not the only way to do it. But I'm confused why it works for > t1.two+1 AS c1 > but not > t1.two+t2.two AS c1 > Those ought to look pretty much the same for this purpose. The bms_overlap(pull_varnos(rcon->root, newnode), rcon->relids) test is false with t1.two+1. Looks like there needs to be a Var from t2 for the bms_overlap to be true David