From: | "Gnanakumar" <gnanam(at)zoniac(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | last_autovacuum & last_autoanalyze showing NULL |
Date: | 2010-08-25 07:30:55 |
Message-ID: | 001e01cb4427$76669a00$6333ce00$@com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Gnanakumar | 2010-08-25 07:33:58 | Re: SQL statements not printed in pgpool log |
Previous Message | Tena Sakai | 2010-08-25 04:25:38 | Re: trouble restoring database |