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 CFA3D3ABEA9 for ; Wed, 22 Dec 2004 16:14:55 +0000 (GMT) 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 42194-03 for ; Wed, 22 Dec 2004 16:14:38 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id CA5BF3AA96B for ; Wed, 22 Dec 2004 16:14:37 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iBMGEaSi004285; Wed, 22 Dec 2004 11:14:36 -0500 (EST) To: ogjunk-pgjedan@yahoo.com Cc: pgsql-admin@postgresql.org Subject: Re: VACUUMing for 30 minutes In-reply-to: <20041222060736.58922.qmail@web12706.mail.yahoo.com> References: <20041222060736.58922.qmail@web12706.mail.yahoo.com> Comments: In-reply-to message dated "Tue, 21 Dec 2004 22:07:36 -0800" Date: Wed, 22 Dec 2004 11:14:36 -0500 Message-ID: <4284.1103732076@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/223 X-Sequence-Number: 15809 writes: > VACUUMing this DB takes about 30 minutes, and during that time the DB > is pretty unresponsive, although the PG process is not using a lot of > CPU (load ~ 1) nor memory (~20MB for the VACUUM process). How big is the DB physically ("du $PGDATA" results)? If you've been lax about vacuuming or not had your FSM parameters set high enough, there could be a whole lot of dead space for VACUUM to scan through. If so, VACUUM FULL or possibly CLUSTER would be the best way to re-compact the tables. (VACUUM VERBOSE on your larger tables would be another way to investigate this.) The other possibility is that you have a seriously slow disk drive :-( regards, tom lane