Re: Remove redundant code in pl_exec.c - Mailing list pgsql-hackers

From Japin Li
Subject Re: Remove redundant code in pl_exec.c
Date
Msg-id MEYP282MB1669B47A5534B2AACC29D893B6439@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Remove redundant code in pl_exec.c  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Remove redundant code in pl_exec.c
List pgsql-hackers
On Fri, 09 Sep 2022 at 23:34, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Japin Li <japinli@hotmail.com> writes:
>> IMO, we can invoke plpgsql_param_eval_generic in plpgsql_param_eval_generic_ro
>> to avoid the redundant.
>
> I don't like this particularly --- it puts way too much premium on
> the happenstance that the MakeExpandedObjectReadOnly call is the
> very last step in the callback function.  If that needed to change,
> we'd have a mess.
>

Sorry, I don't get your mind.  Could you explain it more?  Thanks in advance!

-- 
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.



pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: is_superuser is not documented
Next
From: Justin Pryzby
Date:
Subject: Re: pg_upgrade generated files in subdir follow-up