From: | Pecsök Ján <jan(dot)pecsok(at)profinit(dot)eu> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Reading execution plan - first row time vs last row time |
Date: | 2024-10-01 13:53:18 |
Message-ID: | AS1PR05MB91059DA7056B7C30EAE61AA59F772@AS1PR05MB9105.eurprd05.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dear community,
We see significant difference in explain analyze Actual time in the first line of execution plan and Execution time in the last line of execution plan. What can be the reason?
For example, first line of execution plan:
Gather (cost=1038.49..257627100.42 rows=7943222226 width=104) (actual time=531.925..3673159.806 rows=7943221053 loops=1)
This is 3673159/1000/60 = 61 minutes
And last 2 lines of execution plan:
Planning Time: 3000.399 ms
Execution Time: 21208130.602 ms
This is : 21208130/1000/60= 353 minutes
What happened in 353 - 61 = 292 minutes? We speculate that disk writes. Query possibly written cca 0,75TB of data, by create table as select query.
S pozdravem
Ján Pecsők
Tychonova 2, 160 00 Praha
Mobil: +420 775 942 871
jan(dot)pecsok(at)profinit(dot)eu<mailto:jan(dot)pecsok(at)profinit(dot)eu>
www.profinit.eu<https://www.profinit.eu/>
[cid:image001(dot)png(at)01DB1417(dot)E9060210]<https://www.profinit.eu/>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-10-01 14:07:25 | Re: Question on session timeout |
Previous Message | Greg Sabino Mullane | 2024-10-01 12:14:36 | Re: Question on session timeout |