| From: | Daniel Gustafsson <dgustafsson(at)postgresql(dot)org> |
|---|---|
| To: | Damir Belyalov <dam(dot)bel07(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, a(dot)lepikhov(at)postgrespro(dot)ru |
| Subject: | Re: Output affected rows in EXPLAIN |
| Date: | 2023-09-06 13:20:45 |
| Message-ID: | ABF246A6-E9C6-4562-9723-DE13CF2FA8F9@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 6 Sep 2023, at 14:49, Damir Belyalov <dam(dot)bel07(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2023-09-06 13:35:02 | RE: [PoC] pg_upgrade: allow to upgrade publisher node |
| Previous Message | Ashutosh Bapat | 2023-09-06 13:09:35 | Re: Optimize planner memory consumption for huge arrays |