pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fd Habash <fmhabash@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: What is pg_stat_user_tables Showing NULL for last_autoanalyze & last_autovacuum
Date: Wed, 27 Feb 2019 09:47:13 -0500
Message-ID: <5c76a2f0.1c69fb81.a4b54.6182@mx.google.com> (raw)

I have been able to locate four google search results with the same inquiry. What’ve been able to understand is …

1. If auto-vaccum is working as expected, stats collector does not nullify these values as part of a startup sequence or regular Maitenance. If a relation gets auto[vacuumed|analyzed], the timestamps should remain. 
2. A database engine crash or restart with ‘immediate’ option will cause the timestamps to nullify. 
3. Table never qualified for vacuuming based on auto-vacuum settings. 

I can rule out all three scenarios above, but I still see null values. What else could be at play here? 



----------------
Thank you

view thread (4+ messages)  latest in thread

Message-ID: <5c76a2f0.1c69fb81.a4b54.6182@mx.google.com>
Permalink:  ../5c76a2f0.1c69fb81.a4b54.6182@mx.google.com/
Also on:    postgresql.org/message-id/5c76a2f0.1c69fb81.a4b54.6182@mx.google.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-performance@postgresql.org
  Cc: fmhabash@gmail.com
  Subject: Re: What is pg_stat_user_tables Showing NULL for last_autoanalyze & last_autovacuum
  In-Reply-To: <5c76a2f0.1c69fb81.a4b54.6182@mx.google.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