Re: understanding pg_stat* numbers - Mailing list pgsql-hackers

From Tom Lane
Subject Re: understanding pg_stat* numbers
Date
Msg-id 18156.1111871104@sss.pgh.pa.us
Whole thread Raw
In response to understanding pg_stat* numbers  (Oleg Bartunov <oleg@sai.msu.su>)
Responses Re: understanding pg_stat* numbers
List pgsql-hackers
Oleg Bartunov <oleg@sai.msu.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: minor windows & cygwin regression failures on stable branch
Next
From: Oleg Bartunov
Date:
Subject: Re: understanding pg_stat* numbers