Re: [PERFORM] Explain Analyze - actual time in loops
| От | Igor Neyman |
|---|---|
| Тема | Re: [PERFORM] Explain Analyze - actual time in loops |
| Дата | |
| Msg-id | DM5PR17MB14993F6FD18158C593907D85DA950@DM5PR17MB1499.namprd17.prod.outlook.com обсуждение исходный текст |
| Ответ на | [PERFORM] Explain Analyze - actual time in loops (Neto pr <netopr9@gmail.com>) |
| Ответы |
Re: [PERFORM] Explain Analyze - actual time in loops
|
| Список | pgsql-performance |
From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Neto pr
Sent: Thursday, September 07, 2017 11:17 PM
To: pgsql-performance@postgresql.org
Subject: [PERFORM] Explain Analyze - actual time in loops
…
################################ ###################################
-> Index Scan using idx_l_partkeylineitem000x on lineitem (cost = 0.57..97.65 rows = 26 width = 36)
(current time = 23.615..419.113 rows = 30 loops = 26469)
Index Cond: (l_partkey = part.p_partkey)
################################################## #################
According to the documentation, one should multiply the Actual Time by the number of Loops.
That is: 419113 ms -> 419113/1000/60 = 6.9 minutes * 26469 (loops) = 182.6 minutes.
But how does this stretch take 182.6 minutes, if the entire query ran in 66 minutes?
……………….
thank you and best regards
[] 's Neto
Neto,
The time you see there is in ms, so the point (‘.’) you see is the digital point.
So, it is 419.113ms or a little less than half a second (0.419sec).
Igor Neyman
В списке pgsql-performance по дате отправления: