Re: Row pattern recognition - Mailing list pgsql-hackers

From jian he
Subject Re: Row pattern recognition
Date
Msg-id CACJufxG6rKfd0WtsVZgzcoh8vOEwo_8UDWkuOd888ATavNv_uw@mail.gmail.com
Whole thread
In response to Re: Row pattern recognition  (jian he <jian.universality@gmail.com>)
Responses Re: Row pattern recognition
Re: Row pattern recognition
List pgsql-hackers
On Mon, Jun 15, 2026 at 2:32 PM jian he <jian.universality@gmail.com> wrote:
>
> Hi.
>
> More review based on https://github.com/assam258-5892/postgres/commits/RPR
>

/* arity: a value expression and an optional offset */
Typo: arity

I've attached a patch with some refactoring.
Please note that the inline comments have not yet been updated to
match this refactoring.
The below is detailed commit message.
------------------------------------------------------------------------------------------------
Simplify ParseFuncOrColumn:
It now routes to ParseRPRNavCall exclusively when ParseExprKind is
EXPR_KIND_RPR_DEFINE *and* not column projection *and*
list_length(funcname) == 1.
Original behavior is preserved otherwise.

Centralize error handling:
Treat RPR navigation as FUNCDETAIL_NORMAL to reuse the common error handling in
ParseFuncOrColumn, effectively stripping redundant error checks from
ParseRPRNavCall.

Other miscellaneous code cleanups and minor refactoring.
------------------------------------------------------------------------------------------------



--
jian
https://www.enterprisedb.com/

Attachment

pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: faulty error handling around pgstat_count_io_op_time()
Next
From: Michael Paquier
Date:
Subject: Re: Fix DROP PROPERTY GRAPH "unsupported object class" error