Re: Row pattern recognition

Henson Choi <assam258@gmail.com>

From: Henson Choi <assam258@gmail.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Tatsuo Ishii <ishii@postgresql.org>, david.g.johnston@gmail.com, vik@postgresfriends.org, er@xs4all.nl, peter@eisentraut.org, pgsql-hackers@postgresql.org
Date: 2026-01-15T03:46:16Z
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.champion@enterprisedb.com>님이
작성:

> On Sat, Jan 10, 2026 at 1:20 AM Henson Choi <assam258@gmail.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Adjust cross-version upgrade tests for seg_out() fix

  2. Rationalize error comments in partition split/merge tests

  3. Add fast path for foreign key constraint checks

  4. Fix assorted pretty-trivial memory leaks in the backend.

  5. Add temporal FOREIGN KEY contraints

  6. Add trailing commas to enum definitions

  7. Remove obsolete executor cleanup code