Re: Reading execution plan - first row time vs last row time - Mailing list pgsql-general

From Tom Lane
Subject Re: Reading execution plan - first row time vs last row time
Date
Msg-id 1831449.1727793832@sss.pgh.pa.us
Whole thread Raw
List pgsql-general
=?iso-8859-2?Q?Pecs=F6k_J=E1n?= <jan.pecsok@profinit.eu> writes:
> We see significant difference in explain analyze Actual time in the first line of execution plan and Execution time
inthe 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



pgsql-general by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Reading execution plan - first row time vs last row time
Next
From: George Weaver
Date:
Subject: How to handle "could not find function xml_is_well_formed" when restoring database in Version 17