X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 22B29D1B1D0 for ; Fri, 4 Jun 2004 14:31:04 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34694-01 for ; Fri, 4 Jun 2004 17:30:59 +0000 (GMT) Received: from mail.astudios.com (unknown [66.49.77.3]) by svr1.postgresql.org (Postfix) with ESMTP id 5E1B5D1B187 for ; Fri, 4 Jun 2004 14:30:58 -0300 (ADT) thread-index: AcRKWkzFGHP8PNJmTMOMRuG/ODJtmA== Received: from [10.4.2.252] ([66.194.26.150]) by mail.astudios.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 4 Jun 2004 13:35:16 -0400 Message-ID: <40C0B1C5.3000107@sermonaudio.com> Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132 Date: Fri, 04 Jun 2004 13:30:45 -0400 From: "Chris Hoover" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jeff Boes" Cc: Subject: Re: Setting vacuum_mem for vacuumdb utility References: <200405310248.i4V2mXC28412@candle.pha.pa.us> In-Reply-To: <200405310248.i4V2mXC28412@candle.pha.pa.us> Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 04 Jun 2004 17:35:16.0625 (UTC) FILETIME=[4C9F8010:01C44A5A] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/42 X-Sequence-Number: 13702 Bruce Momjian wrote: >Jeff Boes wrote: >=20=20 > >>I just discovered that the use of a much larger setting on vacuum_mem=20 >>has a joyous effect on the throughput of VACUUM FULL for some of our=20 >>tables. However, all of my maintenance scripts use "vacuumdb" (the=20 >>command-line utility) instead of psql. How can I set vacuum_mem for the= =20 >>duration of the vacuumdb command's execution? >>=20=20=20=20 >> > >Sure, set it in postgresql.conf. > >=20=20 > You can also modify the vacuumdb script. I just added a set call to the=20 script to set the memory to a high value when vacuuming and reset it=20 back to normal when finished so I don't take extra memory away from the=20 server.