Re: [PERFORM] Explain Analyze - actual time in loops

2017-09-08 Thread Tom Lane
Neto pr writes: > I need to know the height of a B-tree index (level of the leaf node > farthest from the root). pageinspect's bt_metap() will give you that --- it's the "level" field, I believe. regards, tom lane -- Sent via pgsql-performance

Re: [PERFORM] Explain Analyze - actual time in loops

2017-09-08 Thread Neto pr
Thanks for reply Tom and Igor. Just only more information: I need to know the height of a B-tree index (level of the leaf node farthest from the root). I tried to find this data in PG_INDEXES and PG_CLASS views, but I did not find it. Does anyone know if Postgresql stores this information,

Re: [PERFORM] Explain Analyze - actual time in loops

2017-09-08 Thread Tom Lane
Neto pr writes: > After analyzing, I saw that in some places of the plan, it is being used > Parallelism. Does this explain why the final value spent (in minutes) to go > through the index (184 minutes) is greater than the total query time (66 > minutes)? I was just about to

Re: [PERFORM] Explain Analyze - actual time in loops

2017-09-08 Thread Neto pr
Igor, You're right, I confused the radix character. But even so the result is approximate to the previous message, 182 minutes, see below: 419.113 / 1000 = 0.41 seconds * 26469 (loops) = 11093.50 seconds or 184 minutes After analyzing, I saw that in some places of the plan, it is being used

Re: [PERFORM] Explain Analyze - actual time in loops

2017-09-08 Thread Igor Neyman
From: pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance-ow...@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 …