Re: possible optimizations - pushing filter before aggregation

Поиск
Список
Период
Сортировка
От Douglas Doole
Тема Re: possible optimizations - pushing filter before aggregation
Дата
Msg-id CADE5jY+izr7SMGVDmhEr6ksRPnYRPOQ_=mXTLyQnT+bsL+T32g@mail.gmail.com
обсуждение исходный текст
Ответ на possible optimizations - pushing filter before aggregation  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: possible optimizations - pushing filter before aggregation
Список pgsql-hackers
Дерево обсуждения

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
---
1
2
3

SELECT * FROM v WHERE m = 2

The 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
---
2

And the minimum of that is 2, which is the wrong answer.

- Doug
Salesforce

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Mail thread references in commits
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Fix checkpoint skip logic on idle systems by tracking LSN progress