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 VI1PR05MB1709ABD41EFF09E4FAAFF4C3C7750@VI1PR05MB1709.eurprd05.prod.outlook.com
Whole thread Raw
In response to Re: [GENERAL] Equivalence Classes when using IN  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-general
> If the only reason that is_simple_subquery() rejects subqueries with
> ORDER BY is due to wanting to keep the order by of a view, then
> couldn't we make is_simple_subquery() a bit smarter and have it check
> if the subquery is going to be joined to something else, which likely
> would destroy the order, or at least it would remove any guarantees of
> it.
>
> Something like the attached?

I dont know if it makes any difference that the ORDER BY is used in a
DISTINCT ON clause. In this case the ORDER BY is important.

- Kim

pgsql-general by date:

Previous
From: Kim Rose Carlsen
Date:
Subject: Re: [GENERAL] Equivalence Classes when using IN
Next
From: Olivani Prisila
Date:
Subject: [GENERAL] [asking about how to upgrade docker postgresql without losing the data]