aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2010-03-18 13:23:57 +0000
committerPeter Eisentraut <peter_e@gmx.net>2010-03-18 13:23:57 +0000
commit12c2f2f66c2d37a951cdf01049d74c520f26e7f9 (patch)
tree271418a9bc86fa610dec2a7a604d5f924e045df6 /src/backend/access/gist/gistscan.c
parentc21ac0b58e8c3bb050d87e213a6f4524b01b2a6d (diff)
downloadpostgresql-12c2f2f66c2d37a951cdf01049d74c520f26e7f9.tar.gz
postgresql-12c2f2f66c2d37a951cdf01049d74c520f26e7f9.zip
Use data-type specific conversion functions also in plpy.execute
In PLy_spi_execute_plan, use the data-type specific Python-to-PostgreSQL conversion function instead of passing everything through InputFunctionCall as a string. The equivalent fix was already done months ago for function parameters and return values, but this other gateway between Python and PostgreSQL was apparently forgotten. As a result, data types that need special treatment, such as bytea, would misbehave when used with plpy.execute.
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions