Horton
Menu

Re: Row pattern recognition

Henson Choi <assam258@gmail.com>

View thread
From: Henson Choi <assam258@gmail.com>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: vik@postgresfriends.org, er@xs4all.nl, jacob.champion@enterprisedb.com, david.g.johnston@gmail.com, peter@eisentraut.org, pgsql-hackers@postgresql.org
Date: 2026-02-19T05:00:21Z
Lists: pgsql-hackers 
Hi Tatsuo,

I noticed that current RPR patches allows to use PREV/NEXT anywhere in
> an SQL statement where normal functions are allowed. According to the
> standard, PREV/NEXT are only allowed in a DEFINE clause. Attached is a
> patch to follow the standard regarding PREV/NEXT.
>

Thanks for the patch! I applied it to my local branch and all
regression tests pass.

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