Re: explain - Mailing list pgsql-general

From Laurenz Albe
Subject Re: explain
Date
Msg-id f40e127d5b9eb5a5ee88489f273292654d3780c6.camel@cybertec.at
Whole thread Raw
In response to Re: explain  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: explain
List pgsql-general
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=941400.77..966327.57 rows=3 width=653) (actual time=52655.694..62533.811 rows=346
loops=1)
> >   Buffers: shared hit=10068265 read=396705 dirtied=1858 written=218, temp read=429687 written=115187
> >   I/O Timings: read=79368.246 write=11.486
> >
> > So, the total execution time is 52655 ms ok
> > and the total time for i/o is...79368 ms
> >
> > how ???
>
> 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=3" or similar then?

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Marc Millas
Date:
Subject: Re: explain
Next
From: Phil Florent
Date:
Subject: pg_comebinebackup