Re: v13 planner ERROR: could not determine which collation to use for string comparison

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: v13 planner ERROR: could not determine which collation to use for string comparison
Дата
Msg-id CAKFQuwazqA2snGEOs2uTV7-Mi5gHknNC1OC3ogx-9HHc8u7t2A@mail.gmail.com
обсуждение исходный текст
Ответ на v13 planner ERROR: could not determine which collation to use for string comparison  (Justin Pryzby <pryzby@telsasoft.com>)
Ответы Re: v13 planner ERROR: could not determine which collation to use for string comparison  (Justin Pryzby <pryzby@telsasoft.com>)
Список pgsql-hackers
Дерево обсуждения
On Tuesday, July 21, 2020, Justin Pryzby <pryzby@telsasoft.com> 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 comparison

I can workaround the issue by DELETEing stats for either column.

It's possible we're doing soemthing wrong and I need to revisit docs..but this
was working in v12.

This sounds suspiciously like a side-effect of:


David J.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: v13 planner ERROR: could not determine which collation to use for string comparison
Следующее
От: Daniel Gustafsson
Дата:
Сообщение: Re: OpenSSL randomness seeding