Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure
Дата
Msg-id 12249.1542824360@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-bugs
"Voillequin, Jean-Marc" <Jean-Marc.Voillequin@moodys.com> writes:
> SIMPLE=> create or replace procedure same_values_proc(a text, b text) as $body$
> SIMPLE$> begin
> SIMPLE$>        assert a = b;
> SIMPLE$> end;$body$ language plpgsql;
> CREATE PROCEDURE
> SIMPLE=>
> SIMPLE=> call same_values_proc(least('a','b'),'a');
> ERROR:  could not determine which collation to use for string comparison
> HINT:  Use the COLLATE clause to set the collation explicitly.

Yeah, same here.  I think somebody forgot to run assign_expr_collations()
on CALL arguments.

            regards, tom lane


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

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15515: DatabaseMetadata.getProcedures and getFunctions returnobjects of either type
Следующее
От: Adrien NAYRAT
Дата:
Сообщение: Re: ALTER INDEX ... ALTER COLUMN not present in dump