Michael Paquier writes:
> On Tue, Jul 21, 2020 at 06:25:00PM -0400, Tom Lane wrote:
>> Ugh. It's clear from your stack trace that neqjoinsel() has forgotten to
>> pass through collation to eqjoinsel(). Will fix.
> Why didn't you include a regression test in bd0d893?
Didn't really see much poin
On Tue, Jul 21, 2020 at 06:25:00PM -0400, Tom Lane wrote:
> Ugh. It's clear from your stack trace that neqjoinsel() has forgotten to
> pass through collation to eqjoinsel(). Will fix.
Why didn't you include a regression test in bd0d893?
--
Michael
signature.asc
Description: PGP signature
Justin Pryzby 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
Reproducer:
postgres=# CREATE TABLE t AS SELECT ''a FROM generate_series(1,99); CREATE
TABLE u AS SELECT ''a FROM generate_series(1,99) ; VACUUM ANALYZE t,u;
postgres=# explain SELECT * FROM t JOIN u ON t.a!=u.a;
ERROR: could not determine which collation to use for string comparison
HINT: Use
On Tuesday, July 21, 2020, Justin Pryzby wrote:
> 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 com
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 fo
