Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> I'm looking for blocks *actually* read from disk, since IO is the most
> important factor.
Well, you won't find that out from Postgres, since it has no idea
whether a read() request was satisfied from kernel disk cache or had
to actually go to disk.
You could turn on log_statement_stats to get some possibly-more-reliable
numbers from the kernel via getrusage(), but this will only tell you
about totals across the whole backend process, not per-relation ...
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Oleg Bartunov||Date: 2005-03-26 21:35:36|
|Subject: Re: understanding pg_stat* numbers |
|Previous:||From: Tom Lane||Date: 2005-03-26 18:22:03|
|Subject: Re: minor windows & cygwin regression failures on stable branch |