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 1jQtWD-0003rQ-Bl for pgsql-docs@arkaria.postgresql.org; Tue, 21 Apr 2020 14:04:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jQtWB-0007WA-9j for pgsql-docs@arkaria.postgresql.org; Tue, 21 Apr 2020 14:04:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jQtWB-0007W3-44 for pgsql-docs@lists.postgresql.org; Tue, 21 Apr 2020 14:04:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jQtW9-0005uk-2C for pgsql-docs@postgresql.org; Tue, 21 Apr 2020 14:04:54 +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 03LE4qmt024517; Tue, 21 Apr 2020 10:04:52 -0400 From: Tom Lane To: =?UTF-8?Q?Marc_Recht=c3=a9?= cc: pgsql-docs@postgresql.org Subject: Re: Where is the qualification par in the Query Tree In-reply-to: <9bce3b37-69d6-cd96-5c7d-dfade984d2c8@rechte.fr> References: <9bce3b37-69d6-cd96-5c7d-dfade984d2c8@rechte.fr> Comments: In-reply-to =?UTF-8?Q?Marc_Recht=c3=a9?= message dated "Tue, 21 Apr 2020 14:49:16 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24515.1587477892.1@sss.pgh.pa.us> Date: Tue, 21 Apr 2020 10:04:52 -0400 Message-ID: <24516.1587477892@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =?UTF-8?Q?Marc_Recht=c3=a9?= writes: > This refers to /doc/src/sgml/html/querytree.html, where one mentions a > qualification part in the Query Tree. While reading the Query node > (parsenode.h) and output from the log with debug_print_parse = on, I > cannot see either this part. Is it gone in profit of join tree ? As noted near the bottom of that documentation page: It turns out to be convenient to store the top-level WHERE expression as a qualification attached to the top-level join-tree item, too. So really the join tree represents both the FROM and WHERE clauses of a SELECT. IOW, Query.jointree->quals. regards, tom lane