pgsql: Change plpgsql's cast cache to consider source typmod as signifi

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Change plpgsql's cast cache to consider source typmod as signifi
Дата
Msg-id E1YTKVT-0003F5-MF@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Change plpgsql's cast cache to consider source typmod as significant.

I had thought that there was no need to maintain separate cache entries
for different source typmods, but further experimentation shows that there
is an advantage to doing so in some cases.  In particular, if a domain has
a typmod (say, "CREATE DOMAIN d AS numeric(20,0)"), failing to notice the
source typmod leads to applying a length-coercion step even when the
source has the correct typmod.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/7f3014dce56c7975113809f2ff5e92cf7c1563a3

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


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Need to special-case RECORD as well as UNKNOWN in plpgsql's cast
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Avoid unused-variable warning in non-assert builds.