From: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Clearing global statistics |
Date: | 2009-12-07 00:44:57 |
Message-ID: | 20091207094457.950B.52131E4D@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> This implements the TODO item "Allow the
> clearing of cluster-level statistics", based on previous discussion
> ending at http://archives.postgresql.org/pgsql-hackers/2009-03/msg00920.php
> -Not sure if this should be named pg_stat_rest_global (to match the way
> these are called "global stats" in the source) or
> pg_stat_reset_cluster. Picked the former for V1, not attached to that
> decision at all. Might even make sense to use a name that makes it
> obvious the pg_stat_bgwriter data is what's targeted.
A couple of comments:
* We will be able to reset global counters and current database's counters.
Do we need to have a method to reset other databases' counters?
Or, will pg_stat_reset_global just reset counters of all databases?
* Is it useful to have a method to reset counters separately?
For example, pg_stat_reset( which text )
which := 'buffers' | 'checkpoints' | 'tables' | 'functions' | ...
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2009-12-07 00:50:11 | Re: Clearing global statistics |
Previous Message | Simon Riggs | 2009-12-06 22:40:58 | Re: Hot standby, recent changes |