Re: BUG #18722: Processing arrays with plpgsql raises errors - Mailing list pgsql-bugs

From Dean Rasheed
Subject Re: BUG #18722: Processing arrays with plpgsql raises errors
Date
Msg-id CAEZATCWKt=XKP12qZhqBX4JaVSatmFwYFnoGYEDDqCbpe-HrEA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18722: Processing arrays with plpgsql raises errors  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #18722: Processing arrays with plpgsql raises errors
List pgsql-bugs
On Sun, 24 Nov 2024 at 22:49, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Here's a fleshed-out patch with a test case and JIT support.  This
> is about the first time I've messed with LLVM, so I wouldn't mind
> some review of what I did in llvmjit_expr.c.  In particular, do I
> correctly understand that "l_funcvalue(b, v_fcinfo, 0)" produces
> a reference to a copy of the initial value of args[0].value?
>

I don't know about that, but I wonder if this bug could be fixed by
having ExecInitExprRec() insert a EEOP_MAKE_READONLY step. Then it
wouldn't be necessary to make any changes to the expression evaluation
code.

Regards,
Dean



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
Next
From: PG Bug reporting form
Date:
Subject: BUG #18724: High data disk utilization during log writing