Re: Logging pg_autovacuum - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Logging pg_autovacuum
Date
Msg-id 20060428201536.GE15566@svana.org
Whole thread Raw
In response to Re: Logging pg_autovacuum  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: Logging pg_autovacuum
List pgsql-hackers
On Fri, Apr 28, 2006 at 04:08:41PM -0400, Robert Treat wrote:
> The first is to add a column(s) to pg_class to hold last vaccum/analyze time
> for each table.  The upsides would be that this puts the information in a
> readily accessable place that can be viewed from third party tools and
> queried against for easier management along with accomplishing what the
> current logging is giving you.

You know, rather than adding new columns to pg_class, why not extend
the stats collector to collect this information. This seems to fall
well within its mandate and it already has the necessary infrastructure
to store info like this. The people likely to want this sort of info
are likely to be running the stats collector anyway. The GUC then
becomes.

stats_autovacuum= on

No more fiddling with log levels or parsing log file, just:

select <the info you want> from pg_stats_autovacuum;

If this table is empty, it isn't running. How often do you want to know
if it was running 5 hours ago?

Thoughts?
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

pgsql-hackers by date:

Previous
From: "Larry Rosenman"
Date:
Subject: Re: Logging pg_autovacuum
Next
From: Tom Lane
Date:
Subject: Re: Logging pg_autovacuum