Horton

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

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Voillequin, Jean-Marc" <Jean-Marc.Voillequin@moodys.com>, pgsql-bugs@lists.postgresql.org, pgsql-sql@lists.postgresql.org
Date: 2019-02-07T07:29:47Z
Lists: pgsql-bugs, pgsql-sql 
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

Commits

  1. Add collation assignment to CALL statement