Re: Row pattern recognition

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: assam258(at)gmail(dot)com
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:38:28
Message-ID: 20260502.133828.1601537265248588543.ishii@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Henson,

> 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.

Ok, from user's point of view, PREV/NEXT/FIRST/LAST and compound forms
are all JIT-compiled. I will add it to the "major changes" section in
the v47 patches posting.

Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhongpu Chen 2026-05-02 04:49:00 Re: Proposal: tighten validation for legacy EUC encodings or document that accepted byte sequences may be unconvertible to UTF8
Previous Message Henson Choi 2026-05-02 04:30:25 Re: Row pattern recognition