Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f98G4Hn96119 for ; Mon, 8 Oct 2001 12:04:17 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f98G3sI01436; Mon, 8 Oct 2001 12:03:54 -0400 (EDT) To: "Summer S. Wilson" cc: pgsql-admin@postgresql.org Subject: Re: Vacuum In-reply-to: <000901c15006$cdd37de0$1b6b5ba5@tamu.edu> References: <000901c15006$cdd37de0$1b6b5ba5@tamu.edu> Comments: In-reply-to "Summer S. Wilson" message dated "Mon, 08 Oct 2001 09:37:48 -0500" Date: Mon, 08 Oct 2001 12:03:54 -0400 Message-ID: <1433.1002557034@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/74 X-Sequence-Number: 2320 "Summer S. Wilson" writes: > I'm running PostgreSQL 7.1 with Slackware 8 on a dual processor Dell server. > I have a database with 17 tables. I started VacuumDB with the analyze > option on Friday around 3pm...when I came in this morning at 8 it was still > not done. From the verbose info, it seems to be "stuck" on one table, > whowrote which is the second largest table (2546 records). Is it consuming CPU time, or just sitting? (ps or top would tell you) If it's just sitting, I'd bet that there is some other connected backend that's holding an open transaction with a lock on that table. regards, tom lane