From: Tom Lane <tgl@sss.pgh.pa.us>
To: ajeesh2705@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17944: Partial index on boolean field is not picked when
 using = while the index is created with is
In-reply-to: <17944-299d21e4e9e90eda@postgresql.org>
References: <17944-299d21e4e9e90eda@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 25 May 2023 14:04:39 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1562855.1685042425.1@sss.pgh.pa.us>
Date: Thu, 25 May 2023 15:20:25 -0400
Message-ID: <1562856.1685042425@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1562856.1685042425%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I have recently created a partial index on tables like following 

> create index unprocessed_order_index
>     on order (creation_date) where processed is false;

> When I am querying the table using processed = false like below, the index
> is not used 

> I was expecting to treat both = and is same, or am I wrong

IS and = are not the same.  You could argue that they have the same effect
in this particular case, but there's no logic in the planner that would
deduce that.

			regards, tom lane