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 DD576D1B17B for ; Tue, 29 Jun 2004 14:09:37 -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 97313-03 for ; Tue, 29 Jun 2004 17:09:33 +0000 (GMT) Received: from jake.bcentralhost.com (jake.bcentralhost.com [205.158.154.24]) by svr1.postgresql.org (Postfix) with ESMTP id 3F631D1B170 for ; Tue, 29 Jun 2004 14:09:31 -0300 (ADT) Received: from [192.168.2.2] ([200.12.238.167]) by jake.bcentralhost.com id NAA26809; Tue, 29 Jun 2004 13:08:37 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Subject: Stopping vacuum From: Werner Bohl Reply-To: wbohl@deepdata.com To: "[ADMIN]" Content-Type: text/plain Organization: Infutor de Costa Rica Message-Id: <1088528969.30410.2.camel@sirio> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 29 Jun 2004 11:09:29 -0600 Content-Transfer-Encoding: 7bit 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/371 X-Sequence-Number: 14031 Hi, We have a very big db that was not vacuumed for a long time. We started vacuum 3 days ago and it has not finished yet. There are some urgent processes that have to be run against the db. Is it safe to kill vacuum? It was started with 'vacuum full analyze' Is there anyway to speed it up at next start? TIA, -- Werner Bohl Infutor de Costa Rica