Re: v13 planner ERROR: could not determine which collation to use for string comparison
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org
Date: 2020-07-22T00:36:12Z
Lists: pgsql-hackers
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
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