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 1wLuKx-00269o-2x for pgsql-hackers@arkaria.postgresql.org; Sun, 10 May 2026 02:56:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wLuKw-00EIjX-22 for pgsql-hackers@arkaria.postgresql.org; Sun, 10 May 2026 02:56:10 +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 1wLuKw-00EIjO-0t for pgsql-hackers@lists.postgresql.org; Sun, 10 May 2026 02:56:10 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wLuKt-00000001Ujf-2ZE0 for pgsql-hackers@postgresql.org; Sun, 10 May 2026 02:56:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=fbjlY6dqjJQTL+N60n8FgMO+S1Qahx+0LOfJ6eXwr8M=; b=k2wb3NueBHfBTWJAD5Kf3FEwaU nxQDAWNVerWuncvnv2n1e5gCwxMdg5ZbxxcZmo3HhZum1eFILGQnGENEUv/pI1y6v3c7m8MEa4/zA 0VJonCzwWeB6FT1LBfq09JG05Cyt3mjtfCgW46/YTm34DXN1aXpJP6ibyM+HgihNtxkF/wg7soQtT 5sRdGrl62m/K338In7sGhDwPJNpihDda9QopA2WxE2sPhR1HcP8IWcDhoq5ZgzgQ3S9h5C/sfREuj pxzVHPAaS1NzmXPlVjvSvGgEcLetNofQ7mU9JX+ggEruUQaCw6E1dFJ9/7yJ+owWL7rnN5zO4A25f fPbERO8g==; Received: from [2409:11:4120:300:e01b:585f:1139:36a0] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wLuKm-004OR5-0s; Sun, 10 May 2026 02:56:01 +0000 Date: Sun, 10 May 2026 11:54:37 +0900 (JST) Message-Id: <20260510.115437.1911555836676501912.ishii@postgresql.org> To: assam258@gmail.com Cc: zsolt.parragi@percona.com, sjjang112233@gmail.com, vik@postgresfriends.org, er@xs4all.nl, jacob.champion@enterprisedb.com, david.g.johnston@gmail.com, peter@eisentraut.org, li.evan.chao@gmail.com, jian.universality@gmail.com, pgsql-hackers@postgresql.org Subject: Re: Row pattern recognition From: Tatsuo Ishii In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:e01b:585f:1139:36a0 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi Henson, > Still deferred: > - B7 Recursive CTE XXX: pending community input on the > ISO/IEC 19075-5 6.17.5 / 4.18.5 interpretation. ISO/IEC 19075-5 6.17.5 stats that "Row pattern matching is prohibited in recursive queries. For example, the following is a syntax error: CREATE RECURSIVE VIEW Problem... SELECT Kolo, Xoro FROM Ticker... WINDOW W AS... MEASURES..." ISO/IEC 19075-5 4.18.5 stats that "Row pattern matching is prohibited in recursive queries. For example, the following is a syntax error: CREATE RECURSIVE VIEW Problem... SELECT Kolo, Xoro FROM t... MATCH_REZOGNIZE..."