From: Gnanakumar <gnanam@zoniac.com>
To: 'Alvaro Herrera' <alvherre@commandprompt.com>
Cc: 'pgsql-admin' <pgsql-admin@postgresql.org>
Subject: Re: Autovacuum daemon internal handling
Date: Fri, 13 Aug 2010 18:36:21 +0530
Message-ID: <005601cb3ae8$559f2d70$00dd8850$@com> (raw)
In-Reply-To: <1281637751-sup-2462@alvh.no-ip.org>
References: <001d01cb3913$0e5c8f60$2b15ae20$@com>
<1281539491-sup-7017@alvh.no-ip.org>
<002401cb39da$bf04aec0$3d0e0c40$@com>
<1281637751-sup-2462@alvh.no-ip.org>
Thanks for the update.
> The main difference is that 8.2 has only one process working at a time,
> whereas in 8.3 and later there can be several. When there's only one
> process, the only way for it to process several databases is
> sequentially; the naptime is how long to sleep between each item in the
> list.
> In 8.3, naptime is the time that lapses between two processes starting,
> while respecting the limit of maximum processes that you configured in
> max_workers. So if the time is already up but all processes are busy
> elsewhere, the next autovacuum will have to wait until one of those
> finishes.
> Since there are multiple processes, you can configure more so that all
> tables can be vacuumed in time.
>> Is there any way to find out the start time of "last_autovaccum" and/or 'last_autoanalyze" for a given table in 8.2.3? So that I can isolate the tables that are taking too long time to complete vacuum and/or analyze and I can perform them externally if need.
> No, I don't think there is in 8.2, unless you crank the debug level down
> to DEBUG2 which means log a lot of stuff (probably too noisy to be
> useful).
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, alvherre@commandprompt.com
Subject: Re: Autovacuum daemon internal handling
In-Reply-To: <005601cb3ae8$559f2d70$00dd8850$@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