Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 41AA0632FFD
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 26 Aug 2010 07:33:01 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 59587-02 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Thu, 26 Aug 2010 10:32:53 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from rs73.luxsci.com (rs73.luxsci.com [64.49.254.135])
	by mail.postgresql.org (Postfix) with ESMTP id 46673632ABF
	for <pgsql-admin@postgresql.org>; Thu, 26 Aug 2010 07:32:53 -0300 (ADT)
Received: from GNANAM (ABTS-TN-Static-186.58.165.122.airtelbroadband.in
	[122.165.58.186] (may be forged)) (authenticated bits=0)
	by rs73.luxsci.com (8.13.8/8.13.8) with ESMTP id o7QAWRD3019973;
	Thu, 26 Aug 2010 05:32:29 -0500
Reply-To: <gnanam@zoniac.com>
From: "Gnanakumar" <gnanam@zoniac.com>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>
Cc: <pgsql-admin@postgresql.org>, <bnichols@ca.afilias.info>
References: <001e01cb4427$76669a00$6333ce00$@com>
	<001001cb445b$c43d8570$4cb89050$@com>
	<19657.1282746788@sss.pgh.pa.us>
In-Reply-To: <19657.1282746788@sss.pgh.pa.us>
Subject: Re: last_autovacuum & last_autoanalyze showing NULL 
Date: Thu, 26 Aug 2010 16:01:41 +0530
Organization: Zoniac Software Private Limited
Message-ID: <003301cb4509$e163afe0$a42b0fa0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActEYnFjcg2csCSfQLiL6MvVfqhraAApgkJw
Content-Language: en-us
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.001 tagged_above=-10 required=5
	tests=BAYES_40=-0.001
X-Spam-Level: 
X-Archive-Number: 201008/231
X-Sequence-Number: 35480

> I don't believe pg_postmaster_start_time() is reset by a
> backend-crash-and-restart sequence ... but the stats collector data will
> be.  You might want to look into the postmaster log for evidence of
> such a crash.

I'm sure that the backend has neither restarted nor crashed at that moment.
Anyway, I've also confirmed this in the server log, I don't find any
evidence or trace of this happened.

Is there any other possible reasons that could make autovacuum daemon to
update it to NULL value?

NOTE: "log_min_messages" is set to NOTICE.