Re: = TRUE vs IS TRUE confuses partition index creation - Mailing list pgsql-bugs

From Tom Lane
Subject Re: = TRUE vs IS TRUE confuses partition index creation
Date
Msg-id 1551758.1660687056@sss.pgh.pa.us
Whole thread Raw
In response to = TRUE vs IS TRUE confuses partition index creation  (Christophe Pettus <xof@thebuild.com>)
Responses Re: = TRUE vs IS TRUE confuses partition index creation
List pgsql-bugs
Christophe Pettus <xof@thebuild.com> 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 by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #17349: Function gen_random_uuid duplicates in pgcrypto and core