Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 489E22E013D for ; Sun, 9 Dec 2007 12:32:29 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 67285-05 for ; Sun, 9 Dec 2007 12:32:25 -0400 (AST) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by postgresql.org (Postfix) with ESMTP id D3E8C2E00BF for ; Sun, 9 Dec 2007 12:32:24 -0400 (AST) Received: by py-out-1112.google.com with SMTP id u77so1761924pyb for ; Sun, 09 Dec 2007 08:32:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=cnd6Qxg2FtsBWheJEjPfPBqARWlg1oZGnrjZdM5uYlQ=; b=CcvymgMajpiJ6H5K7ql2qNHnOAuPKjWoUipfxCQ2nbstjcjKNPHpbvvFE0rhOmF9mmk68BbMnll4gFBm0cqUeD39B3cnrBH9x/ZTrMLDxlgqIN4GlTT7GXP4+FibBMFTRWXKSq7RHec1hpLaKYoZPRqOOnM7eM6x0CF1Y2fLlyA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=Vi2TWTWZvaqlSyCu7Ao+HV1oSX4sRILzQ6EcRxk8rKptq1XD1w4fO4+ZWiXfAq2MurKlG6m32s19DlgJ5xFE75g4duuOK5lZAFEFvFOVX9ydbUpFc4xCgUJDjLkjjPJCMMIDim5CkKCx0HqPY8XVDGGm7UjkpdBOQb4rho519RU= Received: by 10.64.10.2 with SMTP id 2mr11851472qbj.1197217943187; Sun, 09 Dec 2007 08:32:23 -0800 (PST) Received: from ?192.168.1.35? ( [82.2.117.110]) by mx.google.com with ESMTPS id 6sm411716nfv.2007.12.09.08.32.18 (version=SSLv3 cipher=RC4-MD5); Sun, 09 Dec 2007 08:32:21 -0800 (PST) Message-ID: <475C1890.1090804@enterprisedb.com> Date: Sun, 09 Dec 2007 16:32:16 +0000 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.14pre (X11/20071020) MIME-Version: 1.0 To: =?UTF-8?B?SGVydsOpIFBpZWR2YWNoZQ==?= CC: pgsql-performance@postgresql.org Subject: Re: Vacuum full since 15 hours References: <200712091142.41651.bill.footcow@gmail.com> In-Reply-To: <200712091142.41651.bill.footcow@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/111 X-Sequence-Number: 27927 Hervé Piedvache wrote: > I have a small question ... right now on a 8.1.10 version of PostgreSQL I'm > doing a vacuum full verbose anaylze a table with 60 304 340 rows in 1155791 > pages and there were 16 835 144 unused item pointers inside and 5 index. > > After the first treatment of the index (appeared in the verbose) ... the > vacuum is still working now since 15 hours ... There is none other activity > on this server ... it's a replication server ... so the vacuum is locking > most of the replication queries ... > What can I do to get this doing quicker ...? > It's a 8Gb server ... with a RAID 10 ... my maintenance_work_mem = 25600. > > Any idea ? > I'm sure that if I delete all the index an rebuild them by hand it'll be > really quicker ! (done on another replication server ... took 20 min) Yes, it probably will be. IIRC we even suggest doing that in the manual. Another alternative is to run CLUSTER instead of VACUUM FULL. Increasing maintenance_work_mem will make the index builds go faster. Consider if you really need to run VACUUM FULL, or would plain VACUUM be enough. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com