From: Gnanakumar <gnanam@zoniac.com>
To: pgsql-admin@postgresql.org
Cc: bnichols@ca.afilias.info
Subject: Re: last_autovacuum & last_autoanalyze showing NULL
Date: Wed, 25 Aug 2010 19:15:19 +0530
Message-ID: <001001cb445b$c43d8570$4cb89050$@com> (raw)
In-Reply-To: <001e01cb4427$76669a00$6333ce00$@com>
References: <001e01cb4427$76669a00$6333ce00$@com>
> Truncate should not affect those values.
OK.
> Has your Postgres instance crashed or been restarted with immediate mode
since the last vacuum? This will cause the autovacuum information to be
null.
No, it's been up and running for almost a week. I even checked with "select
pg_postmaster_start_time()".
> Also, are you sure that autovacuum has processed these tables at least
once?
Yes, am very sure about this. As I told earlier, I keep tab on this
particular table and even noticed last autovacuum and last autoanalyze every
15 minutes (using cron job I write it to a file) with timestamp before.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gnanam@zoniac.com, bnichols@ca.afilias.info
Subject: Re: last_autovacuum & last_autoanalyze showing NULL
In-Reply-To: <001001cb445b$c43d8570$4cb89050$@com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox