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.