Re: Row pattern recognition

Tatsuo Ishii <ishii@postgresql.org>

From: Tatsuo Ishii <ishii@postgresql.org>
To: pgsql-hackers@postgresql.org
Cc: assam258@gmail.com, jian.universality@gmail.com, zsolt.parragi@percona.com, sjjang112233@gmail.com, vik@postgresfriends.org, er@xs4all.nl, jacob.champion@enterprisedb.com, david.g.johnston@gmail.com, peter@eisentraut.org, li.evan.chao@gmail.com
Date: 2026-06-19T11:39:01Z
Lists: pgsql-hackers

Attachments

Hi,

Attached is the v49 RPR patches. Just rebased. Except that, nothing
has been changed since v48.

> I have created v48 RPR (Row pattern recognition) patches based on the
> attached incremental patches against v47 patches. I have briefly
> looked through all the incremental patches. If I have missed
> something, I will follow up later.  The patches are based on the
> commit 3e3d7875e95 on the master branch.
> 
> The series of patches are to implement the row pattern recognition
> (SQL/RPR) feature. Currently the implementation is a subset of SQL/RPR
> (ISO/IEC 19075-2:2016). Namely, implementation of some features of
> R020 (WINDOW clause). R010 (MATCH_RECOGNIZE) is out of the scope of
> the patches.

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

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