| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com>, Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: explain |
| Date: | 2025-04-24 15:06:52 |
| Message-ID: | f40e127d5b9eb5a5ee88489f273292654d3780c6.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)millas(at)mokadb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Florent | 2025-04-24 18:29:01 | pg_comebinebackup |
| Previous Message | Marc Millas | 2025-04-24 13:51:01 | Re: explain |