From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Clearing global statistics |
Date: | 2009-12-09 17:55:05 |
Message-ID: | 1260381305.12582.0.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On sön, 2009-12-06 at 19:50 -0500, Greg Smith wrote:
> The fact that you're asking the question this way suggests to me I've
> named this completely wrong. pg_stat_reset_global only resets the
> bits
> global to all databases. It doesn't touch any of the
> database-specific
> things that pg_stat_reset can handle right now. At the moment, the
> only
> global information is what's in pg_stat_bgwriter: buffer statistics
> and
> checkpoint stats. I'm thinking that I should rename this new
> function
> to pg_stat_reset_bgwriter so it's obvious how limited its target is.
> Using either "global" or "cluster" for the name is just going to
> leave
> people thinking it acts across a much larger area than it does.
The term "shared" is used elsewhere to describe the, well, shared
catalogs.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-12-09 18:00:22 | Re: Need a mentor, and a project. |
Previous Message | Alvaro Herrera | 2009-12-09 17:12:12 | Re: Build sizes vs docs |