Autovacuum daemon internal handling - Mailing list pgsql-admin

From Gnanakumar
Subject Autovacuum daemon internal handling
Date
Msg-id 001d01cb3913$0e5c8f60$2b15ae20$@com
Whole thread Raw
Responses Re: Autovacuum daemon internal handling
Re: Autovacuum daemon internal handling
List pgsql-admin
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


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: The function of lock file named ".s.PGSQL..lock" on Linux?
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] postgres 9.0 crash when bringing up hot standby