Re: Row pattern recognition

From: Henson Choi <assam258(at)gmail(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, 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-15 03:46:16
Message-ID: CAAAe_zChauRBHQCL+e0DWqDOF41A72hoQ_F1uZb81yzWHD2DFw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Jacob,

Thank you for sharing your dev branch! I extracted test cases from your
implementation and found two failing patterns in my executor:

2026년 1월 15일 (목) AM 3:12, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>님이
작성:

> On Sat, Jan 10, 2026 at 1:20 AM Henson Choi <assam258(at)gmail(dot)com> wrote:
> > I'd definitely be interested in seeing it, rough edges and all. I haven't
> > tackled the PostgreSQL integration design yet, so understanding how
> > preferment rules map to the existing infrastructure would be very
> helpful.
> > (Tatsuo found that email, by the way.)
>
> Yep -- the dev branch link from that email still works, for you and
> anyone interested:
>
> https://github.com/jchampio/postgres/tree/dev/rpr
>

1. (A | B)+ C with data A, B, A, C

My result: NULL (no match)
Correct: 1-4

2. ((A | B) C)+ with data A, C, B, C, X

My result: 1-2, 3-4 (split matches)
Correct: 1-4

> --Jacob
>

Since I implemented the pattern matching and context absorption somewhat
naively,
I think these areas will need an overall review. Thanks for the helpful
test patterns!

Best regards,
Henson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-01-15 03:54:17 Re: Flush some statistics within running transactions
Previous Message jian he 2026-01-15 03:30:41 Re: Enable partitionwise join for partition keys wrapped by RelabelType