On Wed, 2009-07-15 at 14:13 +0200, Rafael Martinez wrote:
> Hello
>
> Should not the execution of pg_stat_reset() reset *all* statistics
> counters everywhere in the database?
It only resets the stats for the current database, not the cluster wide
stats - pg_database is cluster wide.
--
Brad Ni
Brad Nicholson wrote:
> On Wed, 2009-07-15 at 14:13 +0200, Rafael Martinez wrote:
>> Hello
>>
>> Should not the execution of pg_stat_reset() reset *all* statistics
>> counters everywhere in the database?
>
> It only resets the stats for the current database, not the cluster wide
> stats - pg_datab
Rafael Martinez wrote:
> But when we execute pg_stat_reset() in our databases, not all values
> reported by pg_stat_database get updated. tup_returned, tup_fetched,
> tup_inserted, tup_updated and tup_deleted still have the old values
> after running pg_stat_reset().
>
> Am I missing anything?
>
Hello
Should not the execution of pg_stat_reset() reset *all* statistics
counters everywhere in the database?
We would like to use the numbers in pg_stat_database together with
pg_postmaster_start_time() to find out the average values per second of
some of the columns in this view.
But when we e
