24
24
* ParamListInfo arrays are used to pass parameters into the executor
26
26
* to be substituted for a PARAM_EXTERN parameter. The "paramid"
27
27
* of a PARAM_EXTERN Param can range from 1 to numParams.
29
29
* Although parameter numbers are normally consecutive, we allow
30
30
* ptype == InvalidOid to signal an unused array entry.
33
33
* PARAM_FLAG_CONST signals the planner that it may treat this parameter
34
34
* as a constant (i.e., generate a plan that works only for this value
37
37
* There are two hook functions that can be associated with a ParamListInfo
39
39
* isn't null and the executor requires a value for an invalid parameter
40
40
* (one with ptype == InvalidOid), the paramFetch hook is called to give
41
41
* it a chance to fill in the parameter value. Second, a parserSetup