Re: Row pattern recognition

Henson Choi <assam258@gmail.com>

From: Henson Choi <assam258@gmail.com>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: 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, pgsql-hackers@postgresql.org
Date: 2026-06-01T02:29:21Z
Lists: pgsql-hackers
Hi Tatsuo,

> BTW, in v47-0002 patch,
> there are some non ASCII characters ("§").

Good catch -- that one's already handled on top of v47. nocfbot-0004
("Reclassify DEFINE qualifier check and reword diagnostic to 'expression'")
reworded that comment, replacing the section signs with a spelled-out
reference: "prohibited by §6.5" became "prohibited by ISO/IEC 19075-5 6.5",
and likewise for §4.16. The signs you're looking at are an artifact of the
base v47-0002 patch, before that incremental.

To be sure it wasn't lurking elsewhere, I re-swept the whole RPR footprint
-- the sources, the headers, README.rpr, and the regression tests -- and
there are no non-ASCII characters left in the current tree. The fix folds
into v48.

Thanks,
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