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

From Kim Rose Carlsen
Subject Re: [GENERAL] Equivalence Classes when using IN
Date
Msg-id 00313177-8506-43BC-9F6B-2C19F0E5A98B@hiper.dk
Whole thread Raw
In response to Re: [GENERAL] Equivalence Classes when using IN  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] Equivalence Classes when using IN
List pgsql-general
> Yeah.  The ORDER BY creates a partial optimization fence, preventing
> any such plan from being considered.
>>

I can see in the general case it semanticly means different things If you allow the WHERE to pass through ORDER BY.

A special case can be allowed for WHERE to pass the ORDER BY if the column is part of DISTINCT ON.




--
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: rverghese
Date:
Subject: Re: [GENERAL] Making subscribers read only in Postgres 10 logical replication
Next
From: David Rowley
Date:
Subject: Re: [GENERAL] Equivalence Classes when using IN