Re: [GENERAL] Equivalence Classes when using IN - Mailing list pgsql-general

From David Rowley
Subject Re: [GENERAL] Equivalence Classes when using IN
Date
Msg-id CAKJS1f8RHOi-=KjCj51bU+CPpeJyaeYyDQbFL08qaQBEj4U9Gg@mail.gmail.com
Whole thread Raw
In response to [GENERAL] Equivalence Classes when using IN  (Kim Rose Carlsen <krc@hiper.dk>)
Responses Re: [GENERAL] Equivalence Classes when using IN  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [GENERAL] Equivalence Classes when using IN  (Kim Rose Carlsen <krc@hiper.dk>)
List pgsql-general
On 9 October 2017 at 08:01, Kim Rose Carlsen <krc@hiper.dk> wrote:
> Is this because postgres never consider IN clause when building equivalence
> class's?

Only btree equality operators are considered at the moment.

> Are there any interests in adding such rule?

There's been some discussion on it previously, although there is lots
to still be worked out, for example, it's not that clear if it will
always be a win to always apply the qual.

There are more details of the discussion in [1], although there's
probably lots more threads to be found if you search the archives.

[1]
https://www.postgresql.org/message-id/flat/CAKJS1f9FK_X_5HKcPcSeimy16Owe3EmPmmGsGWLcKkj_rW9s6A%40mail.gmail.com#CAKJS1f9FK_X_5HKcPcSeimy16Owe3EmPmmGsGWLcKkj_rW9s6A@mail.gmail.com

-- David Rowley                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Kim Rose Carlsen
Date:
Subject: [GENERAL] Equivalence Classes when using IN
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Equivalence Classes when using IN