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-10T09:20:16Z
Lists: pgsql-hackers
>
> Neat! In case it helps, you may also be interested in my (now very out
> of date) mails at [1] and [2].
>

 Thanks for the pointers! I'll definitely dig into those threads.


> At one point I was also working on an independent implementation of
> the preferment rules, to make it easier for developers to intuit how
> matches were made, but I can't find that email at the moment. This may
> have some overlap with "state visualization" for the engine? I have a
> 3k-line patch based on top of v22 of the patchset as of September
> 2024, if there is interest in that, but no promises on quality -- I
> would have posted it if I thought it was ready for review :D
>

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.)


>
> Thanks,
> --Jacob
>
> [1]
> https://postgr.es/m/96b4d3c8-1415-04db-5629-d2617ac7a156%40timescale.com
> [2]
> https://postgr.es/m/CAGu%3Du8gcyAQAsDLp-01R21%3DM4bpAiGP9PZz0OyiMo5_bM30PMA%40mail.gmail.com


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