Re: Configurable Additional Stats - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Configurable Additional Stats
Date
Msg-id 8495.1183150816@sss.pgh.pa.us
Whole thread Raw
In response to Re: Configurable Additional Stats  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> One way to accomplish the original goal by using the stats
> aggregation/reporting infrastructure directly would be to add a stats_domain
> guc which stats messages get tagged with. So you could have each application
> domain set the guc to a different value and have the stats collector keep
> table stats separately for each stats_domain/table pair.

> That could be interesting for other purposes such as marking a single
> transaction with a new stats_domain so you can look at the stats for
> just that transaction.

Hmm.  That has some possibilities.  You'd want a way to get the stats
collector to discard a domain when you didn't want those numbers
anymore, but that seems doable enough.  Also, most likely you'd want
the collector to keep both "global" and per-domain counters, else
resetting a domain loses state --- which'd be bad from autovac's
point of view, if nothing else.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Configurable Additional Stats
Next
From: Greg Smith
Date:
Subject: Re: Bgwriter LRU cleaning: we've been going at this all wrong