Message-ID: <f40e127d5b9eb5a5ee88489f273292654d3780c6.camel@cybertec.at>
Subject: Re: explain
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: David Rowley <dgrowleyml@gmail.com>, Marc Millas <marc.millas@mokadb.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: Thu, 24 Apr 2025 17:06:52 +0200
In-Reply-To: <CAApHDvqN-mSE=9cgApVfp0qQtuasD_-p6PTRqygT8+HrPtb2zA@mail.gmail.com>
References: 
	<CADX_1aZDtzTaoV5XNi__VbQCj7iPGaU6i5XANjjPwLwF7Acsww@mail.gmail.com>
	 <CAApHDvqN-mSE=9cgApVfp0qQtuasD_-p6PTRqygT8+HrPtb2zA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/f40e127d5b9eb5a5ee88489f273292654d3780c6.camel%40cybertec.at>
Precedence: bulk

On Fri, 2025-04-25 at 01:41 +1200, David Rowley wrote:
> On Fri, 25 Apr 2025 at 01:32, Marc Millas <marc.millas@mokadb.com> wrote:
> > Nested Loop Left Join  (cost=3D941400.77..966327.57 rows=3D3 width=3D65=
3) (actual time=3D52655.694..62533.811 rows=3D346 loops=3D1)
> >   Buffers: shared hit=3D10068265 read=3D396705 dirtied=3D1858 written=
=3D218, temp read=3D429687 written=3D115187
> >   I/O Timings: read=3D79368.246 write=3D11.486
> >=20
> > So, the total execution time is 52655 ms ok
> > and the total time for i/o is...79368 ms
> >=20
> > how ???
>=20
> The 79.3 seconds is the total time spent doing reads for all parallel
> workers. 52.6 seconds is the wall clock time elapsed to execute the
> query.

But wouldn't it read "loops=3D3" or similar then?

Yours,
Laurenz Albe