Re: = TRUE vs IS TRUE confuses partition index creation

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: = TRUE vs IS TRUE confuses partition index creation
Дата
Msg-id
1551758.1660687056@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
= TRUE vs IS TRUE confuses partition index creation Christophe Pettus <xof@thebuild.com>
Re: = TRUE vs IS TRUE confuses partition index creation Tom Lane <tgl@sss.pgh.pa.us>
Re: = TRUE vs IS TRUE confuses partition index creation Richard Guo <guofenglinux@gmail.com>
Re: = TRUE vs IS TRUE confuses partition index creation Richard Guo <guofenglinux@gmail.com>
Re: = TRUE vs IS TRUE confuses partition index creation Tom Lane <tgl@sss.pgh.pa.us>
Re: = TRUE vs IS TRUE confuses partition index creation Richard Guo <guofenglinux@gmail.com>
Re: = TRUE vs IS TRUE confuses partition index creation Tom Lane <tgl@sss.pgh.pa.us>
Christophe Pettus  writes:
> When an index is created on the root of a (declarative) partitioned table, that index is also created on the children, unless there is an existing index on that child that matches the definition of the new index.  It seems that using `= TRUE` confuses it, compared to `IS TRUE`.

IIRC, "b = true" will be simplified to just "b" somewhere in expression
preprocessing.  I'm betting that something in the partitioned index
matching code is applying that preprocessing to one index predicate and
not the other, whereupon they look different.  If that's the explanation,
there are likely other cases that should match and fail to.

			regards, tom lane


В списке pgsql-bugs по дате отправления
От: Daniel Gustafsson
Дата:
От: Bruce Momjian
Дата:
FAQ