Re: v13 planner ERROR: could not determine which collation to use for string comparison
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2020-07-21T19:57:57Z
Lists: pgsql-hackers
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 the COLLATE clause to set the collation explicitly.
Commits
-
neqjoinsel must now pass through collation to eqjoinsel.
- bd0d893aa7aa 14.0 landed
- cc4dd2a7af13 13.0 landed
- 171633ff5d8e 12.4 landed
-
Use query collation, not column's collation, while examining statistics.
- 022cd0bfd339 12.4 cited