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 CAKJS1f-uCHFXOb6H6rVH+msh3+d4YyZFd5F1Ax7tzuFsXsrwyw@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Equivalence Classes when using IN  (Kim Rose Carlsen <krc@hiper.dk>)
Responses Re: [GENERAL] Equivalence Classes when using IN  (Kim Rose Carlsen <krc@hiper.dk>)
List pgsql-general
On 12 October 2017 at 08:37, Kim Rose Carlsen <krc@hiper.dk> wrote:
>
>> 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.

Yeah, we do allow predicates to be pushed down in that case.

-- 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: Re: [GENERAL] Equivalence Classes when using IN
Next
From: Kim Rose Carlsen
Date:
Subject: Re: [GENERAL] Equivalence Classes when using IN