Re: Row pattern recognition

From: Henson Choi <assam258(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, peter(at)eisentraut(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Row pattern recognition
Date: 2026-01-17 08:33:28
Message-ID: CAAAe_zDRjXLMyZ_nanAbnq-+4Gq42N7JgKUBqKAm09RVCzTECg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2026년 1월 17일 (토) 17:19, Tatsuo Ishii <ishii(at)postgresql(dot)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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2026-01-17 08:38:43 Re: Row pattern recognition
Previous Message Tatsuo Ishii 2026-01-17 08:18:50 Re: Row pattern recognition