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 50EC6D1B1CD for ; Tue, 29 Jun 2004 23:41:48 -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 70501-03 for ; Wed, 30 Jun 2004 02:41:49 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 49C62D1B17B for ; Tue, 29 Jun 2004 23:41:44 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i5U2fmss002787; Tue, 29 Jun 2004 22:41:48 -0400 (EDT) To: wbohl@deepdata.com Cc: "[ADMIN]" Subject: Re: Stopping vacuum In-reply-to: <1088528969.30410.2.camel@sirio> References: <1088528969.30410.2.camel@sirio> Comments: In-reply-to Werner Bohl message dated "Tue, 29 Jun 2004 11:09:29 -0600" Date: Tue, 29 Jun 2004 22:41:47 -0400 Message-ID: <2786.1088563307@sss.pgh.pa.us> From: Tom Lane 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/384 X-Sequence-Number: 14044 Werner Bohl writes: > 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? It is safe in the sense that your database won't be corrupted (were it not safe, vacuum would be too dangerous to use at all --- think of power failures for instance). However, whatever work vacuum has done on the current table will be lost and need to be done over when you run it again. If the thing is stuck on a particularly large and messy table then killing it could well be counterproductive --- you might just be buying yourself an even longer vacuum run next time. I'd suggest identifying exactly which table it is currently working on before you kill it. Then look into alternate methods of compacting that table. It's entirely possible that CLUSTER would be a faster cleanup method than VACUUM FULL. regards, tom lane