Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 728FA9FA4A7 for ; Sat, 30 Sep 2006 13:45:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 69933-09 for ; Sat, 30 Sep 2006 16:45:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 62FA19FA3A0 for ; Sat, 30 Sep 2006 13:45:52 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k8UGjoj6013552; Sat, 30 Sep 2006 12:45:50 -0400 (EDT) To: "Nimesh Satam" cc: pgsql-performance@postgresql.org Subject: Re: Table not getting vaccumed. In-reply-to: <965aa3ed0609300225v33a3a6d4s9b19568d75949cc3@mail.gmail.com> References: <965aa3ed0609300225v33a3a6d4s9b19568d75949cc3@mail.gmail.com> Comments: In-reply-to "Nimesh Satam" message dated "Sat, 30 Sep 2006 14:55:54 +0530" Date: Sat, 30 Sep 2006 12:45:50 -0400 Message-ID: <13551.1159634750@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/443 X-Sequence-Number: 21129 "Nimesh Satam" writes: > I am trying to vaccum one of the table using the following command: > VACUUM FULL ANALYZE VERBOSE table_name; > But for some reason the table vaccuming is not going ahead. VACUUM FULL requires exclusive lock on the table, so it's probably waiting for some open transaction that has a reader's or writer's lock on it. Look in pg_stat_activity and pg_locks to find out more. regards, tom lane