Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure
Date
Msg-id 66209b1a-db5b-d578-6674-1be789c581f5@2ndquadrant.com
Whole thread Raw
In response to Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure
Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure
List pgsql-bugs
On 21/11/2018 19:19, Tom Lane wrote:
> "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.

This appears to fix it.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: BUG #15511: Drop table error "invalid argument"
Next
From: Tom Lane
Date:
Subject: Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure