Commit3200b15

committed

Remove comment claiming that PARAM_EXTERN Params always have typmod -1.

This hasn't been true in quite some time, cf plpgsql's make_datum_param().

1 parent934d122 commit3200b15Copy full SHA for 3200b15

File tree

-8

lines changed

-8

lines changed

Lines changed: 3 additions & 8 deletions

Original file line number	Diff line number	Diff line change
`@@ -179,9 +179,10 @@ typedef struct Const`
`179`	`179`	`intlocation;/* token location, or -1 if unknown */`
`180`	`180`	`}Const;`
`181`	`181`
`182`		`-/* ----------------`
	`182`	`+/*`
`183`	`183`	`* Param`
`184`		`- *paramkind - specifies the kind of parameter. The possible values`
	`184`	`+ *`
	`185`	`+ *paramkind specifies the kind of parameter. The possible values`
`185`	`186`	`*for this field are:`
`186`	`187`	`*`
`187`	`188`	`*PARAM_EXTERN: The parameter value is supplied from outside the plan.`
`@@ -204,12 +205,6 @@ typedef struct Const`
`204`	`205`	*of the `paramid' field contain the SubLink's subLinkId, and
`205`	`206`	`*the low-order 16 bits contain the column number. (This type`
`206`	`207`	`*of Param is also converted to PARAM_EXEC during planning.)`
`207`		`- *`
`208`		`- * Note: currently, paramtypmod is always -1 for PARAM_EXTERN params, since`
`209`		`- * the APIs that supply values for such parameters don't carry any typmod`
`210`		`- * info. It is valid in other types of Params, if they represent expressions`
`211`		`- * with determinable typmod.`
`212`		`- * ----------------`
`213`	`208`	`*/`
`214`	`209`	`typedefenumParamKind`
`215`	`210`	`{`

Comments

(0)