pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gnanakumar <gnanam@zoniac.com>
To: pgsql-admin@postgresql.org
Subject: Autovacuum daemon internal handling
Date: Wed, 11 Aug 2010 10:37:08 +0530
Message-ID: <001d01cb3913$0e5c8f60$2b15ae20$@com> (raw)

Hi,

Our production server is running PostgreSQL v8.2.3 on Red Hat Enterprise
Linux Server release 5 (Tikanga).

I need a clarification on how autovacuum daemon internally works/handles in
the following specific use case/situation:

1. Does autovacuum daemon works with one table at a time or does it work
with multiple tables at the same time? 
Reason to ask this question is, let's say I've "autovacuum_naptime" set to 1
minute, and there are 500 tables in one database.   Assuming there are 10
tables that has to be vacuumed and analyzed based on the threshold defined
in one of the autovacuum daemon execution time, and if takes more than 1
minute to complete vacuum and analyze operation on even a single table (out
of 10 tables), how does autovacuum daemon works/handles in this case?

2. The columns "last_autovaccum" and 'last_autoanalyze" in
pg_stat_user_tables shows the start time or end time of the operation?

Regards,
Gnanam




view thread (6+ messages)  latest in thread

Message-ID: <001d01cb3913$0e5c8f60$2b15ae20$@com>
Permalink:  ../001d01cb3913$0e5c8f60$2b15ae20$@com/
Also on:    postgresql.org/message-id/001d01cb3913$0e5c8f60$2b15ae20$@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
  Subject: Re: Autovacuum daemon internal handling
  In-Reply-To: <001d01cb3913$0e5c8f60$2b15ae20$@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