pgsql: Need to special-case RECORD as well as UNKNOWN in plpgsql's cast

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Need to special-case RECORD as well as UNKNOWN in plpgsql's cast
Дата
Msg-id E1YTJNY-00029V-Nl@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/45f2c2fc4e4adcf75cd689e18dab77ebe622fc2e

Modified Files
--------------
src/pl/plpgsql/src/pl_exec.c |    9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Use standard casting mechanism to convert types in plpgsql, when
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Change plpgsql's cast cache to consider source typmod as signifi