From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: v13 planner ERROR: could not determine which collation to use for string comparison
Date: Tue, 21 Jul 2020 18:25:00 -0400
Message-ID: <1199426.1595370300@sss.pgh.pa.us> (raw)
In-Reply-To: <20200721191606.GL5748@telsasoft.com>
References: <20200721191606.GL5748@telsasoft.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pryzby@telsasoft.com
Subject: Re: v13 planner ERROR: could not determine which collation to use for string comparison
In-Reply-To: <1199426.1595370300@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox