Re: Row pattern recognition - Mailing list pgsql-hackers

From Henson Choi
Subject Re: Row pattern recognition
Date
Msg-id CAAAe_zDRjXLMyZ_nanAbnq-+4Gq42N7JgKUBqKAm09RVCzTECg@mail.gmail.com
Whole thread Raw
In response to Re: Row pattern recognition  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: Row pattern recognition
List pgsql-hackers


2026년 1월 17일 (토) 17:19, Tatsuo Ishii <ishii@postgresql.org>님이 작성:
Hi Henson,

> I'm now reviewing the remaining parts: pattern optimization in planner,
> absorption function, and step function. Once the review is complete,
> I'll send the rest of the patches.

I am reviewing the test cases and found this:

SELECT * FROM (SELECT 1 AS x) t
 WINDOW w AS (
 ROWS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING
 PATTERN (a b c d e f g h i j k l m n o p q r s t u v w x y z aa)
 DEFINE a AS TRUE
);
ERROR:  number of row pattern definition variable names exceeds 26

I thought you have eliminated the 26 variables limit. If so, related
codes using WindowClause->defineInitial should be removed. Shall I do
that? Or you want to do that while refactoring?


Already found and cleaned up.
Will include it in the next patch.​​​​​​​​​​​​​​​​


Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Row pattern recognition
Next
From: Tatsuo Ishii
Date:
Subject: Re: Row pattern recognition