| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pecsök Ján <jan(dot)pecsok(at)profinit(dot)eu> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Reading execution plan - first row time vs last row time |
| Date: | 2024-10-01 14:43:52 |
| Message-ID: | 1831449.1727793832@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?iso-8859-2?Q?Pecs=F6k_J=E1n?= <jan(dot)pecsok(at)profinit(dot)eu> writes:
> We see significant difference in explain analyze Actual time in the first line of execution plan and Execution time in the last line of execution plan. What can be the reason?
The time reported for the top query node is just the time taken to
compute all the rows returned by the query. It doesn't account
for what might be done with the data afterward. A normal EXPLAIN
just drops that data on the floor, so there's not much time left
unaccounted-for. But if you're writing the data into a table via
EXPLAIN CREATE TABLE AS, that I/O would be extra.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | George Weaver | 2024-10-01 17:08:58 | How to handle "could not find function xml_is_well_formed" when restoring database in Version 17 |
| Previous Message | Greg Sabino Mullane | 2024-10-01 14:39:11 | Re: Reading execution plan - first row time vs last row time |