| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | "Voillequin, Jean-Marc" <Jean-Marc(dot)Voillequin(at)moodys(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: | 2019-02-05 14:46:27 |
| Message-ID: | 19783.1549377987@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-sql |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 21/11/2018 19:19, Tom Lane wrote:
>> Yeah, same here. I think somebody forgot to run assign_expr_collations()
>> on CALL arguments.
> This appears to fix it.
I think this should be fine as a band-aid patch. As I mentioned
previously, I'm not really happy with our generally-unprincipled
approach to where collation assignment is called from ... but a
bug-fix patch should probably not be tasked with making that
better. Especially not with less than a week till 11.2.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-02-05 16:51:17 | Re: BUG #15620: pgAdmin IV pgAgent multi-schedule jobs messed up view of schedules |
| Previous Message | Peter Eisentraut | 2019-02-05 14:11:32 | Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-02-07 07:29:47 | Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |
| Previous Message | Peter Eisentraut | 2019-02-05 14:11:32 | Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |