Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id F1174B5DBC6 for ; Sat, 9 Jul 2011 06:27:10 -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 29770-06 for ; Sat, 9 Jul 2011 09:27:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from aoskar.kilobug.org (kilobug.org [62.212.118.231]) by mail.postgresql.org (Postfix) with ESMTP id B5757B5D803 for ; Sat, 9 Jul 2011 06:27:04 -0300 (ADT) Received: from kilobug by aoskar.kilobug.org with local (Exim 4.72) (envelope-from ) id 1QfToS-0002x2-RT; Sat, 09 Jul 2011 11:27:00 +0200 From: Gael Le Mignot To: Guillaume Lelarge Cc: Gael Le Mignot , pgsql-performance@postgresql.org Subject: Re: Memory usage of auto-vacuum Organization: Pilot Systems References: <1310200383.2101.8.camel@laptop> <1310201594.2101.12.camel@laptop> <1310202377.2101.15.camel@laptop> Mail-Copies-To: nobody X-Revolutionnary-Date: 21 Messidor an 219 de la =?iso-8859-1?Q?R=E9volutio?= =?iso-8859-1?Q?n?= X-PGP-Fingerprint: 1F2C 9804 7505 79DF 95E6 7323 B66B F67B 7103 C5DA Date: Sat, 09 Jul 2011 11:27:00 +0200 In-Reply-To: <1310202377.2101.15.camel@laptop> (Guillaume Lelarge's message of "Sat, 09 Jul 2011 11:06:16 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201107/61 X-Sequence-Number: 44273 Hello Guillaume! Sat, 09 Jul 2011 11:06:16 +0200, you wrote: > On Sat, 2011-07-09 at 11:00 +0200, Gael Le Mignot wrote: >> Hello Guillaume! >> >> Sat, 09 Jul 2011 10:53:14 +0200, you wrote: >> >> > I don't quite understand how you can get up to 1GB used by your process. >> > According to your configuration, and unless I'm wrong, it shouldn't take >> > more than 40MB. Perhaps a bit more, but not 1GB. So, how did you find >> > this number? >> >> Looking at "top" we saw the postgres process growing and growing and >> then shrinking back, and doing a "select * from pg_stat_activity;" in >> parallel of the growing we found only the "vacuum analyze" query running. >> > There is not only one postgres process. So you first need to be sure > that it's the one that executes the autovacuum. Shouldn't "pg_stat_activity" contain the current jobs of all the processes ? >> But maybe we drawn the conclusion too quickly, I'll try disabling the >> auto vacuum to see if we really get rid of the problem doing it. >> > Disabling the autovacuum is usually a bad idea. You'll have to execute > VACUUM/ANALYZE via cron, which could get hard to configure. Oh, yes, sure, I meant as a test to know if it's the vacuum or not, not to definitely disable it. > BTW, what's your PostgreSQL release? I assume at least 8.3 since you're > using FTS? It's 8.4 from Debian Squeeze. -- Gaël Le Mignot - gael@pilotsystems.net Pilot Systems - 9, rue Desargues - 75011 Paris Tel : +33 1 44 53 05 55 - www.pilotsystems.net Gérez vos contacts et vos newsletters : www.cockpit-mailing.com