Re: How can the Aggregation move to the outer query

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: How can the Aggregation move to the outer query
Date: 2021-05-25 11:42:44
Message-ID: CAApHDvpxgWX=cQgF4mWZhbdisiy-V0U+dHAEipHhswjyM8OQBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 25 May 2021 at 22:28, Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> wrote:
>
> explain (costs off) select (select count(*) filter (where t2.b = 1) from m1 t1)
> from m1 t2 where t2.b % 2 = 1;
>
> QUERY PLAN
> -------------------------------
> Aggregate
> -> Seq Scan on m1 t2
> Filter: ((b % 2) = 1)
> SubPlan 1
> -> Seq Scan on m1 t1
> (5 rows)
>
> This one is too confusing to me since the Aggregate happens
> on t2 rather than t1. What happens here? Would this query
> generate 1 row all the time like SELECT aggfunc(a) FROM t?

I think you're misreading the plan. There's a scan on t2 with a
subplan then an aggregate on top of that. Because you made the
subquery correlated by adding t2.b, it cannot be executed as an
initplan.

You might see what's going on better if you add VERBOSE to the EXPLAIN options.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2021-05-25 11:51:38 Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c)
Previous Message Peter Eisentraut 2021-05-25 11:36:16 Re: Fixing the docs for ALTER SUBSCRIPTION ... ADD/DROP PUBLICATION