Re: v13 planner ERROR: could not determine which collation to use for string comparison

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: v13 planner ERROR: could not determine which collation to use for string comparison
Date: 2020-07-21 22:25:00
Message-ID: 1199426.1595370300@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Justin Pryzby <pryzby(at)telsasoft(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-07-21 22:53:07 Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Previous Message Tom Lane 2020-07-21 22:18:26 Re: Infinities in type numeric