Re: possible optimizations - pushing filter before aggregation
От | Pavel Stehule |
---|---|
Тема | Re: possible optimizations - pushing filter before aggregation |
Дата | |
Msg-id | CAFj8pRAgfM+7sdyHL5gfhPStu9C3TZH5ZRizCvKaVUaas9GjUQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: possible optimizations - pushing filter before aggregation (Douglas Doole <dougdoole@gmail.com>) |
Ответы |
Re: possible optimizations - pushing filter before aggregation
|
Список | pgsql-hackers |
2016-11-19 3:59 GMT+01:00 Douglas Doole <dougdoole@gmail.com>:
On Fri, Nov 18, 2016 at 12:47 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:Isn't possible in this case push equivalence before aggregation?If I'm understanding you correctly, that would lead to wrong results. Here's a simple example:CREATE VIEW v AS SELECT MIN(a) m FROM t;and table T contains:T:A---123SELECT * FROM v WHERE m = 2The minimum value of A is 1, so the query should return no rows.However, if we filter first we'd be effectively doing the query:SELECT MIN(a) m FROM(SELECT a FROM t WHERE a=2) AS v(a)The subquery is going to return an intermediate result of:V:A---2And the minimum of that is 2, which is the wrong answer.
yes, you have true,
thank you for correcting
Regards
Pavel
- DougSalesforce
В списке pgsql-hackers по дате отправления: