Re: transformJsonFuncExpr pathspec cache lookup failed - Mailing list pgsql-hackers

From jian he
Subject Re: transformJsonFuncExpr pathspec cache lookup failed
Date
Msg-id CACJufxHBjjP_=KMOuVqHJU4MJaRBi1pse2B9M=-VTwTJBp-zYg@mail.gmail.com
Whole thread Raw
In response to Re: transformJsonFuncExpr pathspec cache lookup failed  (Kirill Reshke <reshkekirill@gmail.com>)
List pgsql-hackers
On Fri, Nov 7, 2025 at 2:26 PM Kirill Reshke <reshkekirill@gmail.com> wrote:
>
> Hi!
> I tried your fix and this indeed fixes an issue. Two minor comments:
>
> First,
> in the `src/backend/parser/parse_expr.c` fil there are multiple
> examples of working with `coerce_to_target_type`, they all share
> different coding practice:
>
> ```
> coerced_expr = coerce_to_target_type(.., expr, ..)
>
> if (coerced_expr == NULL)
>      ereport();
>
>
> expr = coerced_expr;
> ```
>
> Instead of
> ```
> expr = coerce_to_target_type(.., expr, ..)
>
> if (expr == NULL)
>      ereport();
> ```
>
> Let's be consistent?
>

IMHO,
> coerced_expr = coerce_to_target_type(.., expr, ..)
is better than
> expr = coerce_to_target_type(.., expr, ..)

I changed accordingly.

Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: PRI?64 vs Visual Studio (2022)
Next
From: Chao Li
Date:
Subject: Re: [PATCH] Add pg_get_tablespace_ddl() function to reconstruct CREATE TABLESPACE statement