| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-07 07:29:47 |
| Message-ID: | 6e40d0c0-2605-ce2f-cae5-0e4a0d0e305f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-sql |
On 05/02/2019 15:46, Tom Lane wrote:
> 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.
committed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2019-02-07 07:49:56 | Re: BUG #15613: Bug in PG Planner for Foreign Data Wrappers |
| Previous Message | Peter Geoghegan | 2019-02-07 00:18:55 | Re: BUG #15597: possible bug in amcheck/amcheck_next (or corrupted index?) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | github kran | 2019-02-11 21:14:53 | Aurora Postgresql RDS DB Latency |
| Previous Message | Tom Lane | 2019-02-05 14:46:27 | Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure |