Re: Row pattern recognition
Henson Choi <assam258@gmail.com>
From: Henson Choi <assam258@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tatsuo Ishii <ishii@postgresql.org>, jacob.champion@enterprisedb.com, david.g.johnston@gmail.com, vik@postgresfriends.org, er@xs4all.nl, peter@eisentraut.org, pgsql-hackers@postgresql.org
Date: 2026-01-19T23:51:30Z
Lists: pgsql-hackers
Hi Michael, 2026년 1월 20일 (화) AM 8:40, Michael Paquier <michael@paquier.xyz>님이 작성: > On Mon, Jan 19, 2026 at 12:32:40AM +0900, Henson Choi wrote: > > I'm writing to document the detailed design of context absorption > > optimization in Row Pattern Recognition (RPR). This is mainly for > > future reference - honestly, I'm afraid I'll forget these details > > myself in a few months, and I'd rather have them written down > > somewhere public than buried in my notes. I don't want to repeat the > > mistake of famous mathematical theorems > > where brilliant ideas were lost because "the margin was too narrow > > to contain the proof" (yes, I'm looking at you, Fermat!). I certainly > > don't want future PostgreSQL hackers to spend the next 358 years > > trying to re-implement context absorption because the design rationale > > was lost. Fortunately, the PostgreSQL community has provided us with > > sufficient digital margins. :) > > Note: this message is clearly AI-generated to me, and these are > usually super sloppy. (I'd suggest to stop posting semi-generated > messages as they tend to be made of mostly unhelpful contents as they > lack judgement and context, but there's no rule against that AFAIK > around here, as well.) > Fair point. I can read technical documentation but lack English communication skills, so I rely on AI for translation. Actually, AI is what enabled me to start contributing to PostgreSQL in the first place. I'll try to make future posts more readable. > -- > Michael > Thanks for the feedback. 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 →
-
Adjust cross-version upgrade tests for seg_out() fix
- 3e3d7875e956 19 (unreleased) cited
-
Rationalize error comments in partition split/merge tests
- ecb2508aaf9b 19 (unreleased) cited
-
Add fast path for foreign key constraint checks
- 2da86c1ef9b5 19 (unreleased) cited
-
Fix assorted pretty-trivial memory leaks in the backend.
- e78d1d6d47dc 19 (unreleased) cited
-
Add temporal FOREIGN KEY contraints
- 89f908a6d0ac 18.0 cited
-
Add trailing commas to enum definitions
- 611806cd726f 17.0 cited
-
Remove obsolete executor cleanup code
- d060e921ea5a 17.0 cited