From: | "Shoaib Mir" <shoaibmir(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_statio_all_indexes |
Date: | 2006-07-30 18:16:40 |
Message-ID: | bf54be870607301116j1e67c977n2ae745d114cc5f26@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)hoksza(at)seznam(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-30 18:24:33 | Re: pg_statio_all_indexes |
Previous Message | David Hoksza | 2006-07-30 17:54:32 | pg_statio_all_indexes |