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.96) (envelope-from ) id 1wdSYQ-00474N-0e for pgsql-docs@arkaria.postgresql.org; Sat, 27 Jun 2026 12:54:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wdSYN-00FFVd-35 for pgsql-docs@arkaria.postgresql.org; Sat, 27 Jun 2026 12:54:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wd7h2-00Ba7C-06 for pgsql-docs@lists.postgresql.org; Fri, 26 Jun 2026 14:38:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wd7gz-00000000N12-1lHg for pgsql-docs@lists.postgresql.org; Fri, 26 Jun 2026 14:38:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=94eekia318YKPx+08r4nTGCX/2QRbq3JwrtmBXFFe8g=; b=JkpzZvCvbxyEfa/2FMJINOeL0w sEtyOygUnMueFAzX7/BddmqmX5PL8OfcGII9DU6c7bloG+17C9E4iKOJJD+rHOvnBhUtN6RovsGdp oFNO23qq1sNDxvixNFDF0JhSKOYLIuPEyB5IbeVH6E/X+pHmGO4CmQOrrqyyRLdiPm2XDtF9eOcIh 4oDMT5bohUHGe7EsdRABjWrKqatXKQ9k9F39MAr+BjQmUZLag1hHxbwVGr1qE/yq+e63fFFu3BcnQ FVK/MNhP1QyGXUAY4PNUpCQYMA7BJAD5ZjjXZEH+g714Me5GnkN5H0q4yU5HNvrgdffIlfB1DEi7j 6Cbgl2QQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wd7gy-006rSD-0O for pgsql-docs@lists.postgresql.org; Fri, 26 Jun 2026 14:38:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wd7gw-002gSO-38 for pgsql-docs@lists.postgresql.org; Fri, 26 Jun 2026 14:38:02 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Check query To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: y.saburov@gmail.com Reply-To: y.saburov@gmail.com, pgsql-docs@lists.postgresql.org Date: Fri, 26 Jun 2026 14:37:56 +0000 Message-ID: <178248467618.108999.9966122434342474006@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/rules-views.html Description: Please check that the condition in the query is correct. > 39.2.1. How SELECT Rules Work Similarly, the rules for shoe and shoelace are substituted into the range table of the subquery, leading to a three-level final query tree: SELECT shoe_ready.shoename, shoe_ready.sh_avail, shoe_ready.sl_name, shoe_ready.sl_avail, shoe_ready.total_avail ... ... WHERE shoe_ready.total_avail > 2; ??? (maybe WHERE shoe_ready.total_avail >=3D 2;)