Re: Monitoring Object access

From: Satoshi Nagayasu <satoshi(dot)nagayasu(at)gmail(dot)com>
To: adi hirschtein <adiso75(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org
Subject: Re: Monitoring Object access
Date: 2010-09-14 16:55:13
Message-ID: 4C8FA8F1.5040606@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2010/09/12 23:02, adi hirschtein wrote:
> I'm coming from the Oracle side of the house and In oracle for instance, you use shared buffer as well, but you are still able to see which session is waiting for which blocks
> and if one session is doing the "real" I/O then the other one wait on 'wait for other session" event so you are able to know who did the actual I/O
> the reason behind it is that you want to check which objects is being heavily hit by which business processes or users and then tier your storage accordingly.
> I agree with your point about the OS buffer cache, I need to monitor it as well.
> is there any place rather than pg_stat_activity that you think I should take a look at?

I think you should also look at pg_locks to know
which session is processing (or waiting on locks).

http://www.postgresql.org/docs/8.4/interactive/view-pg-locks.html

pg_locks table contains several lock information
including "lock dependencies" which you may need
to monitor session activities.

--
NAGAYASU Satoshi <satoshi(dot)nagayasu(at)gmail(dot)com>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alan Hodgson 2010-09-14 17:44:35 Re: Post Install / Secure PostgreSQL
Previous Message Carlos Mennens 2010-09-14 16:50:30 Re: Post Install / Secure PostgreSQL