Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Weird "could not determine which collation to use for string comparison" with LEAST/GREATEST on PG11 procedure
Date
Msg-id 19783.1549377987@sss.pgh.pa.us
Whole thread Raw
In response to Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-bugs
Tree view 
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.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Weird "could not determine which collation to use for stringcomparison" with LEAST/GREATEST on PG11 procedure
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #15620: pgAdmin IV pgAgent multi-schedule jobs messed upview of schedules