| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | assam258(at)gmail(dot)com |
| Cc: | vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Row pattern recognition |
| Date: | 2026-02-17 09:00:53 |
| Message-ID: | 20260217.180053.64368434967157940.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Henson,
>> What do you mean by "Anchored pattern" here? I am asking because R010
>> (RPR in Window clause) does not allow to use anchors (^ and $) in
>> PATTERN clause.
>>
>
> Good catch - the term "anchored pattern" is indeed confusing here.
> You're absolutely right that SQL:2023 R010 does not allow regex anchors
> (^ and $) in the PATTERN clause.
> In this context, I was using "anchored" to mean "a pattern that starts
> with a PREFIX element" - not referring to regex anchors at all. The
> example "START A+ B" has a PREFIX element (START) that "anchors" the
> pattern matching to begin at a specific point.
Ok.
> To avoid confusion with SQL regex anchors, I suggest we change the
> terminology:
>
> "Anchored pattern" → "Pattern with PREFIX" or "PREFIX-led pattern"
I like "Pattern with PREFIX".
> "Anchored pattern absorption" → "PREFIX pattern absorption optimization"
Looks good.
> The optimization issue remains the same: PREFIX elements block the
> absorption mechanism, requiring the "shadow path" approach to maintain
> O(n) complexity while processing patterns like "START A+ B".
> Does this clarification make sense?
Yes!
Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-02-17 09:19:29 | amcheck: add index-all-keys-match verification for B-Tree |
| Previous Message | Michael Paquier | 2026-02-17 08:59:31 | Re: Our ABI diff infrastructure ignores enum SysCacheIdentifier |