Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id B3D7F475E5F for ; Sun, 12 May 2002 11:46:57 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id C6F2B475E3E for ; Sun, 12 May 2002 11:46:21 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g4CFkOW29932; Sun, 12 May 2002 11:46:24 -0400 (EDT) To: Brian McCane Cc: pgsql-admin Subject: Re: VACUUM FULL In-reply-to: <20020511120040.X12454-100000@fw.mccons.net> References: <20020511120040.X12454-100000@fw.mccons.net> Comments: In-reply-to Brian McCane message dated "Sat, 11 May 2002 12:10:00 -0500" Date: Sun, 12 May 2002 11:46:24 -0400 Message-ID: <29929.1021218384@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200205/102 X-Sequence-Number: 4277 Brian McCane writes: > Also, I disabled my nightly VACUUM ANALYZE from cron while I was doing > this because I was unsure what would happen with multiple VACUUM's > running. Multiple VACUUMs work fine (except possibly for driving your system load to the moon ;-)). Somewhere back around 6.5 I think we had problems with that due to sloppy interlocking, but it's been fixed for a long time. regards, tom lane