Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 8623C65014C for ; Wed, 26 Nov 2008 10:26:21 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61328-05 for ; Wed, 26 Nov 2008 10:26:18 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-out2.uio.no (mail-out2.uio.no [129.240.10.58]) by mail.postgresql.org (Postfix) with ESMTP id 8F94565021E for ; Wed, 26 Nov 2008 10:26:17 -0400 (AST) Received: from mail-mx5.uio.no ([129.240.10.46]) by mail-out2.uio.no with esmtp (Exim 4.69) (envelope-from ) id 1L5LLL-0002zL-K8; Wed, 26 Nov 2008 15:26:15 +0100 Received: from bbking.uio.no ([129.240.6.205]) by mail-mx5.uio.no with esmtpsa (TLSv1:AES256-SHA:256) user rafael (Exim 4.69) (envelope-from ) id 1L5LLL-0000Xl-AS; Wed, 26 Nov 2008 15:26:15 +0100 Message-ID: <492D5C87.5090505@usit.uio.no> Date: Wed, 26 Nov 2008 15:26:15 +0100 From: Rafael Martinez User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: Rafael Domiciano CC: "pgsql-admin@postgresql.org" Subject: Re: Vacuum Problems References: <3a0028490811260543x74d02719w775a457999cfc74@mail.gmail.com> In-Reply-To: <3a0028490811260543x74d02719w775a457999cfc74@mail.gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 347B79E2D60D98A5EC3DA5F46D0F7CA7E4C97715 X-UiO-SPAM-Test: remote_host: 129.240.6.205 spam_score: -49 maxlevel 200 minaction 2 bait 0 mail/h: 2 total 1739 max/h 29 blacklist 0 greylist 0 ratelimit 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/149 X-Sequence-Number: 30803 Rafael Domiciano wrote: Hei > I need some help or just some hints. I am having problems with vacuum > full in one table only: "clifatura". > That table has today around 7 million rows. > How big is the database? > I scheduled on the server a cron job to run VACUUM FULL every day at 23 > P.M, but on the following day, at 8 A.M. vacuum is yet working on > "clifatura"; so I have to kill vacuum. > Do you have any locks in this table/database that prevent the vacuum to be started? Why do you use VACUUM FULL everyday? This will lock your database until it finish. I can count with one hand the times we had to run vacuum full in our systems in the last 6 years. Use a normal vacuum analyze if 'autovacuum' is not enough for you. -- Rafael Martinez, Center for Information Technology Services University of Oslo, Norway PGP Public Key: http://folk.uio.no/rafael/