Reply-To: <gnanam@zoniac.com>
From: "Gnanakumar" <gnanam@zoniac.com>
To: <pgsql-admin@postgresql.org>
Subject: last_autovacuum & last_autoanalyze showing NULL
Date: Wed, 25 Aug 2010 13:00:55 +0530
Organization: Zoniac Software Private Limited
Message-ID: <001e01cb4427$76669a00$6333ce00$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: ActEJ3O8YUN1CjcGR1y1iam04eqnYQ==
Content-Language: en-us

Hi,

Our production server is running PostgreSQL v8.2.3 on RHEL5.  Autovacuum
daemon is also running in the server.

A brief background on my use case:  We heavily use a table for storing of
data temporarily inside PostgreSQL functions.  Eventually, there will not be
any record in the table.  Because this table is used heavily, I usually keep
tab of this particular table in "pg_stat_user_tables", so that disk space is
within control.

Recently, I noticed that "last_autovacuum" and "last_autoanalyze" column for
this table showing a <NULL> value.  My question here is, what
condition/scenario would make this column to update to <NULL> value by
autovacuum?  I can add one more point here, which I remember, that is I
performed a TRUNCATE on this table just before.  I believe that this is not
because of TRUNCATE  TABLE?

Regards,
Gnanam