From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Dave Page" <dpage(at)postgresql(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Configurable Additional Stats |
Date: | 2007-06-29 19:46:35 |
Message-ID: | 876456mtlw.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> So far it sounds terribly badly designed --- for starters, apparently it's
> intending to ignore the stats aggregation/reporting infrastructure and
> reinvent that wheel in some unspecified way, for unspecified reasons.
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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-06-29 20:05:25 | Re: Configurable Additional Stats |
Previous Message | Tom Lane | 2007-06-29 19:28:21 | Re: Configurable Additional Stats |