From: | "Gnanakumar" <gnanam(at)zoniac(dot)com> |
---|---|
To: | "'Alvaro Herrera'" <alvherre(at)commandprompt(dot)com> |
Cc: | "'pgsql-admin'" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Autovacuum daemon internal handling |
Date: | 2010-08-13 13:06:21 |
Message-ID: | 005601cb3ae8$559f2d70$00dd8850$@com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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).
From | Date | Subject | |
---|---|---|---|
Next Message | Gnanakumar | 2010-08-13 13:24:02 | SQL statements not printed in pgpool log |
Previous Message | Raymond O'Donnell | 2010-08-13 12:37:25 | Re: [ODBC] PGexpress v4.11 + postgresql 8.4.4 |