Postgres Pro
Downloads
Home   >   mailing lists

Re: v13 planner ERROR: could not determine which collation to use for string comparison - Mailing list pgsql-hackers

From Tom Lane
Subject Re: v13 planner ERROR: could not determine which collation to use for string comparison
Date
Msg-id 1199426.1595370300@sss.pgh.pa.us
Whole thread Raw
In response to v13 planner ERROR: could not determine which collation to use for string comparison  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: v13 planner ERROR: could not determine which collation to use for string comparison  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
Justin Pryzby <pryzby@telsasoft.com> writes:
> We hit this on v13b2 and verified it fails on today's HEAD (ac25e7b039).
> explain SELECT 1 FROM sites NATURAL JOIN sectors WHERE sites.config_site_name != sectors.sect_name ;
> ERROR:  could not determine which collation to use for string comparison

> I can workaround the issue by DELETEing stats for either column.

Ugh.  It's clear from your stack trace that neqjoinsel() has forgotten to
pass through collation to eqjoinsel().  Will fix.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Infinities in type numeric
Next
From: Peter Geoghegan
Date:
Subject: Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)