Skip site navigation (1) Skip section navigation (2)

Re: understanding pg_stat* numbers

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: understanding pg_stat* numbers
Date: 2005-04-01 09:29:57
Message-ID: d2j4op$1c9t$ (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
"Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su> writes
> One mystery remains, why stats show heap_blks_read > 0 for indexed search
>      select 1 from foo where id=5
> I did pg_stat_reset() before run query.

There is no clustered index in PG so far, so all the data item has to be
stay in the heap. In brief, the executor has to check the visibility of each
row in the heap pointed by the index. For performance consideration, if one
row is invisible("killed"), PG could remember its status it in the index
item identifier, so next time it just ignore it.


In response to

pgsql-hackers by date

Next:From: Thomas HallgrenDate: 2005-04-01 11:44:39
Subject: Re: Name change proposal
Previous:From: Neil ConwayDate: 2005-04-01 08:41:41
Subject: Re: [HACKERS] contrib/pg_buffercache

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group