diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2010-08-18 12:20:15 +0000 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2010-08-18 12:20:15 +0000 |
| commit | ef71375346f8eba52ab3ec8b360869f859c83f3e (patch) | |
| tree | 538dc354a5822ab911d026fff1a600eee7f18939 /src/backend/executor/nodeModifyTable.c | |
| parent | 9a8d15bd41687e1448bcc441adb5e183d5fdcaf2 (diff) | |
| download | postgresql-ef71375346f8eba52ab3ec8b360869f859c83f3e.tar.gz postgresql-ef71375346f8eba52ab3ec8b360869f859c83f3e.zip | |
Coerce 'unknown' type parameters to the right type in the fixed-params
parse_analyze() function. That case occurs e.g with PL/pgSQL
EXECUTE ... USING 'stringconstant'.
The coercion with a CoerceViaIO node. The result is similar to the coercion
via input function performed for unknown constants in coerce_type(),
except that this happens at runtime.
Backpatch to 9.0. The issue is present in 8.4 as well, but the coerce param
hook infrastructure this patch relies on was introduced in 9.0. Given the
lack of user reports and harmlessness of the bug, it's not worth attempting
a different fix just for 8.4.
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions