public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tatsuo Ishii <[email protected]>
To: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: Row pattern recognition
Date: Sat, 17 Jan 2026 17:18:50 +0900 (JST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAAAe_zC1Ui2=xjoPQ_9CAfP4vPW6utFWc+a7Vb_j_aaBB0YM4Q@mail.gmail.com>
References: <[email protected]>
	<CAAAe_zAUSSiEgNSiwQSRd2FT094rC3BoCJawqERDOv-fZ97rKw@mail.gmail.com>
	<CAAAe_zC1Ui2=xjoPQ_9CAfP4vPW6utFWc+a7Vb_j_aaBB0YM4Q@mail.gmail.com>

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?

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

view thread (7+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Row pattern recognition
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox