diff options
author | Tom Lane | 2011-04-12 23:19:24 +0000 |
---|---|---|
committer | Tom Lane | 2011-04-12 23:19:24 +0000 |
commit | d64713df7e5996ab3ab337b5e0901cf2c53773f9 (patch) | |
tree | 7105a61bf9fef5cef674cea7f1305dfeb77aa39a /src/backend/tcop/fastpath.c | |
parent | 88543ecfec9c754b5f14b898bccbc68d941748b3 (diff) |
Pass collations to functions in FunctionCallInfoData, not FmgrInfo.
Since collation is effectively an argument, not a property of the function,
FmgrInfo is really the wrong place for it; and this becomes critical in
cases where a cached FmgrInfo is used for varying purposes that might need
different collation settings. Fix by passing it in FunctionCallInfoData
instead. In particular this allows a clean fix for bug #5970 (record_cmp
not working). This requires touching a bit more code than the original
method, but nobody ever thought that collations would not be an invasive
patch...
Diffstat (limited to 'src/backend/tcop/fastpath.c')
-rw-r--r-- | src/backend/tcop/fastpath.c | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/src/backend/tcop/fastpath.c b/src/backend/tcop/fastpath.c index d0a23d007aa..30863bb7b96 100644 --- a/src/backend/tcop/fastpath.c +++ b/src/backend/tcop/fastpath.c @@ -349,8 +349,12 @@ HandleFunctionRequest(StringInfo msgBuf) /* * Prepare function call info block and insert arguments. + * + * Note: for now we pass collation = InvalidOid, so collation-sensitive + * functions can't be called this way. Perhaps we should pass + * DEFAULT_COLLATION_OID, instead? */ - InitFunctionCallInfoData(fcinfo, &fip->flinfo, 0, NULL, NULL); + InitFunctionCallInfoData(fcinfo, &fip->flinfo, 0, InvalidOid, NULL, NULL); if (PG_PROTOCOL_MAJOR(FrontendProtocol) >= 3) rformat = parse_fcall_arguments(msgBuf, fip, &fcinfo); |