X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id C4AA6D1B507 for ; Wed, 17 Sep 2003 22:19:19 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 18964-01 for ; Wed, 17 Sep 2003 19:19:08 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 15484D1B4F0 for ; Wed, 17 Sep 2003 19:19:03 -0300 (ADT) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3651602; Wed, 17 Sep 2003 15:19:35 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: "Matt Clark" , Subject: Re: Is there a reason _not_ to vacuum continuously? Date: Wed, 17 Sep 2003 15:17:26 -0700 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200309171517.26841.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/253 X-Sequence-Number: 3619 Matt, > I understand this needs an exclusive lock on the whole table, which is > simply not possible more than once a month, if that... Workarounds/hack > suggestions are more than welcome :-) Would it be reasonable to use partial indexes on the table? --=20 -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco