From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?iso-8859-2?Q?Pecs=F6k_J=E1n?= <jan.pecsok@profinit.eu>
cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: Reading execution plan - first row time vs last row time
In-reply-to: <AS1PR05MB91059DA7056B7C30EAE61AA59F772@AS1PR05MB9105.eurprd05.prod.outlook.com>
References: <AS1PR05MB91059DA7056B7C30EAE61AA59F772@AS1PR05MB9105.eurprd05.prod.outlook.com>
Comments: In-reply-to =?iso-8859-2?Q?Pecs=F6k_J=E1n?= <jan.pecsok@profinit.eu>
	message dated "Tue, 01 Oct 2024 13:53:18 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1831448.1727793832.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 01 Oct 2024 10:43:52 -0400
Message-ID: <1831449.1727793832@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1831449.1727793832%40sss.pgh.pa.us>
Precedence: bulk

=3D?iso-8859-2?Q?Pecs=3DF6k_J=3DE1n?=3D <jan.pecsok@profinit.eu> writes:
> We see significant difference in explain analyze Actual time in the firs=
t 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