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 6e40d0c0-2605-ce2f-cae5-0e4a0d0e305f@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>)
List pgsql-bugs
On 05/02/2019 15:46, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.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


pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #15597: possible bug in amcheck/amcheck_next (or corrupted index?)
Next
From: Etsuro Fujita
Date:
Subject: Re: BUG #15613: Bug in PG Planner for Foreign Data Wrappers