| From: | Henson Choi <assam258(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | zsolt(dot)parragi(at)percona(dot)com, sjjang112233(at)gmail(dot)com, vik(at)postgresfriends(dot)org, er(at)xs4all(dot)nl, jacob(dot)champion(at)enterprisedb(dot)com, david(dot)g(dot)johnston(at)gmail(dot)com, peter(at)eisentraut(dot)org, li(dot)evan(dot)chao(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Row pattern recognition |
| Date: | 2026-05-02 04:30:25 |
| Message-ID: | CAAAe_zCe1gj_UkapC4e_GVZmud+dxru8YONpKRhtY6c2RmXcZg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Tatsuo,
I know in v47 JIT compilation supports PREV/NEXT. What about
> FIRST/LAST and compound forms?
>
Yes, those are JIT-compiled too in v47.
The JIT side only deals with two opcodes -- EEOP_RPR_NAV_SET
and EEOP_RPR_NAV_RESTORE.
FIRST/LAST and the compound forms differ only in how
ExecEvalRPRNavSet() computes target_pos for the slot swap;
the opcode interface and the call into ExecEvalRPRNavSet /
ExecEvalRPRNavRestore are unchanged.
So 0018's JIT support carries over to FIRST/LAST and
compounds without any JIT-side change.
Regards,
Henson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2026-05-02 04:38:28 | Re: Row pattern recognition |
| Previous Message | Tatsuo Ishii | 2026-05-02 04:17:18 | Re: Row pattern recognition |