Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 2A78BB5DBC6 for ; Sat, 9 Jul 2011 05:39:40 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 90078-10 for ; Sat, 9 Jul 2011 08:39:34 +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 EEC69B5DBC4 for ; Sat, 9 Jul 2011 05:39:33 -0300 (ADT) Received: from kilobug by aoskar.kilobug.org with local (Exim 4.72) (envelope-from ) id 1QfT4V-0002iK-9B; Sat, 09 Jul 2011 10:39:31 +0200 From: Gael Le Mignot To: Craig Ringer Cc: pgsql-performance@postgresql.org Subject: Re: Memory usage of auto-vacuum Organization: Pilot Systems References: <4E1811F3.80705@postnewspapers.com.au> 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 10:39:30 +0200 In-Reply-To: <4E1811F3.80705@postnewspapers.com.au> (Craig Ringer's message of "Sat, 09 Jul 2011 16:31:47 +0800") 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/56 X-Sequence-Number: 44268 Hello Craig! Sat, 09 Jul 2011 16:31:47 +0800, you wrote: > On 9/07/2011 3:25 PM, Gael Le Mignot wrote: >> >> Hello, >> >> We are running a PostgreSQL 8.4 database, with two tables containing a >> lot (> 1 million) moderatly small rows. It contains some btree indexes, >> and one of the two tables contains a gin full-text index. >> >> We noticed that the autovacuum process tend to use a lot of memory, >> bumping the postgres process near 1Gb while it's running. > What is maintenance_work_mem set to in postgresql.conf? It's the debian default, which is 16Mb. Do you think we should reduce it ? I also forgot to add something which may be important : there are a lot of INSERT (and SELECT) in those tables, but very few UPDATE/DELETE. Regards, -- 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