Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 4D69E6328FC for ; Fri, 13 Aug 2010 10:07:11 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 39115-03 for ; Fri, 13 Aug 2010 13:07:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from rs73.luxsci.com (rs73.luxsci.com [64.49.254.135]) by mail.postgresql.org (Postfix) with ESMTP id D2DF0632866 for ; Fri, 13 Aug 2010 10:07:02 -0300 (ADT) Received: from GNANAM (ABTS-TN-Static-186.58.165.122.airtelbroadband.in [122.165.58.186] (may be forged)) (authenticated bits=0) by rs73.luxsci.com (8.13.8/8.13.8) with ESMTP id o7DD6thr024516; Fri, 13 Aug 2010 08:06:57 -0500 Reply-To: From: "Gnanakumar" To: "'Alvaro Herrera'" Cc: "'pgsql-admin'" References: <001d01cb3913$0e5c8f60$2b15ae20$@com> <1281539491-sup-7017@alvh.no-ip.org> <002401cb39da$bf04aec0$3d0e0c40$@com> <1281637751-sup-2462@alvh.no-ip.org> In-Reply-To: <1281637751-sup-2462@alvh.no-ip.org> Subject: Re: Autovacuum daemon internal handling Date: Fri, 13 Aug 2010 18:36:21 +0530 Organization: Zoniac Software Private Limited Message-ID: <005601cb3ae8$559f2d70$00dd8850$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acs6TPajtPIS2dvpQC+ZsCYf5bUxMgAmwaXA Content-Language: en-us X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.001 tagged_above=-10 required=5 tests=BAYES_40=-0.001 X-Spam-Level: X-Archive-Number: 201008/105 X-Sequence-Number: 35354 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).