pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gnanakumar <gnanam@zoniac.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Cc: bnichols@ca.afilias.info
Subject: Re: last_autovacuum & last_autoanalyze showing NULL
Date: Thu, 26 Aug 2010 16:01:41 +0530
Message-ID: <003301cb4509$e163afe0$a42b0fa0$@com> (raw)
In-Reply-To: <19657.1282746788@sss.pgh.pa.us>
References: <001e01cb4427$76669a00$6333ce00$@com>
	<001001cb445b$c43d8570$4cb89050$@com>
	<19657.1282746788@sss.pgh.pa.us>

> 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.




view thread (5+ messages)

Message-ID: <003301cb4509$e163afe0$a42b0fa0$@com>
Permalink:  ../003301cb4509$e163afe0$a42b0fa0$@com/
Also on:    postgresql.org/message-id/003301cb4509$e163afe0$a42b0fa0$@com

 · 

reply

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, tgl@sss.pgh.pa.us, bnichols@ca.afilias.info
  Subject: Re: last_autovacuum & last_autoanalyze showing NULL
  In-Reply-To: <003301cb4509$e163afe0$a42b0fa0$@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