From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | raghavendra t <raagavendra(dot)rao(at)gmail(dot)com> |
Cc: | tv(at)fuzzy(dot)cz, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dynamic Catalog Views |
Date: | 2010-04-13 17:24:11 |
Message-ID: | 4BC4A8BB.5090609@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
raghavendra t wrote:
> Can we get the dynamic information like in oracle(v$) views. Same as
> in postgresql buffers(shared,temp,wal) & cache(maintainence_work_me,
> effective_mem).
The information available in this area includes:
1) Look at buffer cache hit rates using pg_stat_user_tables,
pg_statio_user_tables, pg_stat_user_indexes, and pg_statio_user_indexes
2) Dig into pg_buffercache to find out what's sitting in RAM and how
well the usage count implementation is working for you
3) Monitor pg_stat_bgwriter to find out what checkpoints are doing
4) Turn on log_temp_files (8.3 or later) to log when work_mem is being
exceeded and sorts are going to disk.
That's really it; the rest of the sort of data that's available in the
v$ views isn't exposed in nearly as much detail in PostgreSQL yet.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-04-13 18:37:25 | Re: C-language functions: SRF question |
Previous Message | raghavendra t | 2010-04-13 17:04:26 | Re: Dynamic Catalog Views |