Horton
Menu

Re: Output affected rows in EXPLAIN

Daniel Gustafsson <dgustafsson@postgresql.org>

View thread
From: Daniel Gustafsson <dgustafsson@postgresql.org>
To: Damir Belyalov <dam.bel07@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, a.lepikhov@postgrespro.ru
Date: 2023-09-06T13:20:45Z
Lists: pgsql-hackers 
> On 6 Sep 2023, at 14:49, Damir Belyalov <dam.bel07@gmail.com> wrote

> The patch fixes this problem.

Given that EXPLAIN ANALYZE has worked like for a very long time, which problem
is it you have identified?

I'm also not convinced that the added "EXPLAIN" in the below plan is an
improvement in any way.

postgres=# explain (analyze) select * from t;
                                          QUERY PLAN
-----------------------------------------------------------------------------------------------
 Seq Scan on t  (cost=0.00..35.50 rows=2550 width=4) (actual time=0.064..0.075 rows=5 loops=1)
 Planning Time: 1.639 ms
 Execution Time: 0.215 ms
(3 rows)

EXPLAIN
postgres=#

--
Daniel Gustafsson