diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-03-04 19:10:57 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-03-04 19:10:57 -0500 |
commit | 45f2c2fc4e4adcf75cd689e18dab77ebe622fc2e (patch) | |
tree | 52e6ddb17e68e2387269ff0e0ca920357a1ca37d /src/backend/access/transam/xloginsert.c | |
parent | 1345cc67bbb014209714af32b5681b1e11eaf964 (diff) |
Need to special-case RECORD as well as UNKNOWN in plpgsql's casting logic.
This is because can_coerce_type thinks that RECORD can be cast to any
composite type, but coerce_record_to_complex only works for inputs that are
RowExprs or whole-row Vars, so we get a hard failure on a CaseTestExpr.
Perhaps these corner cases ought to be fixed so that coerce_to_target_type
actually returns NULL as per its specification, rather than failing ...
but for the moment an extra check here is the path of least resistance.
Diffstat (limited to 'src/backend/access/transam/xloginsert.c')
0 files changed, 0 insertions, 0 deletions