From: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Passing estate to assign_simple_var() |
Date: | 2018-03-15 10:55:44 |
Message-ID: | CAE9k0Pnhry9+BAkTjJ1+YuJM5iCC+YJhPXwvZ97zpzkfETVv5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi All,
I don't see any reason for passing estate variable to
assign_simple_var() in the current postgreSQL code. I think, it was
required earlier as we were updating param info in this function but,
now, we are not doing that here. So, shouldn't it be removed. Thoughts
?
I think, the ides of not updating param info inside this function got
changed as a part of the following git commit.
Rearrange execution of PARAM_EXTERN Params for plpgsql's
benefit.
This patch does three interrelated things:
* Create a new expression execution step type EEOP_PARAM_CALLBACK
and add the infrastructure needed for add-on modules to generate that.
As discussed, the best control mechanism for that seems to be to add
another hook function to ParamListInfo, which will be called by
ExecInitExpr if it's supplied and a PARAM_EXTERN Param is found.
For stand-alone expressions, we add a new entry point to allow the
ParamListInfo to be specified directly, since it can't be retrieved
from the parent plan node's EState.
--
With Regards,
Ashutosh Sharma
EnterpriseDB:http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2018-03-15 10:59:43 | Re: [HACKERS] GSoC 2017: weekly progress reports (week 4) and patch for hash index |
Previous Message | Alvaro Herrera | 2018-03-15 10:35:03 | Re: Failed to request an autovacuum work-item in silence |