Re: pg_statio_all_indexes - Mailing list pgsql-general

From Shoaib Mir
Subject Re: pg_statio_all_indexes
Date
Msg-id bf54be870607301116j1e67c977n2ae745d114cc5f26@mail.gmail.com
Whole thread Raw
In response to pg_statio_all_indexes  (David Hoksza <david.hoksza@seznam.cz>)
List pgsql-general
As per my understanding, 'pg_statio_all_indexes' displays "idx_blks_hit" using "pg_stat_get_blocks_hit(oid)" where the function "pg_stat_get_blocks_hit" gets number of disk block requests found in cache for a table or index.

Hope this helps...

Thanks,
 --
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 7/30/06, David Hoksza <david.hoksza@seznam.cz> wrote:
Hi, I'm not sure about the value idx_blks_hit of pg_statio_all_indexes
view. Is it total value of touched pages, or do I get total value when
I add idx_blks_read to it?
In other words - does idx_blks_hit cover also physical reads?

Thanks,
       David Hoksza



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match




pgsql-general by date:

Previous
From: David Hoksza
Date:
Subject: pg_statio_all_indexes
Next
From: Tom Lane
Date:
Subject: Re: pg_statio_all_indexes