Re: Redundant database objects.

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Andrew Bartley <ambartley(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Redundant database objects.
Date: 2010-07-12 23:45:13
Message-ID: 4C3BA909.2050106@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andrew Bartley wrote:
> Unfortunately these views only give me what appears to be a certain
> time frame. This does not help all that much. It will give a list of
> tables, indexes and sequences that have been used in the time frame,
> so that is at least a start.

You can use pg_stat_reset() to set those back to 0 again and then see
what actually gets used moving forward from the point you do that.
That's a reasonable idea to do anyway to make all those statistics
better reflect recent activity rather than historical. Just be warned
that it will screw up many monitoring systems if you have them pointed
toward those statistics tables and grabbing snapshots, some will view
the reset as the values going negative which doesn't make any real-world
sense.

--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Bartley 2010-07-13 00:09:48 Re: Redundant database objects.
Previous Message Andrew Bartley 2010-07-12 23:22:05 Re: Redundant database objects.