Re: Row pattern recognition
Henson Choi <assam258@gmail.com>
From: Henson Choi <assam258@gmail.com>
To: Tatsuo Ishii <ishii@postgresql.org>, jian.universality@gmail.com
Cc: 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-18T10:43:51Z
Lists: pgsql-hackers
Hi Tatsuo, Thanks -- I'll go in this direction; your sketch has the shape of it. > Yes, I think the direction is correct. Probably the patch would someting > like this? > > + update_reduced_frame(winstate->nav_winobj, > + winstate->frameheadpos); Right: drive the match once per row, up front, instead of letting frame access drive it. That's the plan, with two refinements on top of the sketch. First, a small refactor: I'll pull the reduced-frame loop and the mark advance out into their own functions, called once per row before the window functions run -- so the match tracks the row scan rather than frame reads. Second, the mark: I'll advance it per NFA row from the match frontier rather than the output row, so the tuplestore is trimmed as soon as the match is done with each row. 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 →
-
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