"Tom Lane" <tgl@sss.pgh.pa.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
