| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Voillequin, Jean-Marc" <Jean-Marc(dot)Voillequin(at)moodys(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, pgsql-sql(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |
| Date: | 2018-11-21 18:19:20 |
| Message-ID: | 12249.1542824360@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-sql |
"Voillequin, Jean-Marc" <Jean-Marc(dot)Voillequin(at)moodys(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrien NAYRAT | 2018-11-21 18:24:18 | Re: ALTER INDEX ... ALTER COLUMN not present in dump |
| Previous Message | Voillequin, Jean-Marc | 2018-11-21 14:09:55 | Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Williams | 2018-11-26 19:12:39 | Select Distinct Order By Array_Position |
| Previous Message | Voillequin, Jean-Marc | 2018-11-21 14:09:55 | Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |