X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 685F5D1B439 for ; Wed, 17 Dec 2003 05:30:59 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 68158-08 for ; Wed, 17 Dec 2003 01:30:28 -0400 (AST) Received: from mallard.mail.pas.earthlink.net (mallard.mail.pas.earthlink.net [207.217.120.48]) by svr1.postgresql.org (Postfix) with ESMTP id A2B6DD1B43A for ; Wed, 17 Dec 2003 01:30:27 -0400 (AST) Received: from hsa158.pool003.at101.earthlink.net ([216.249.70.158] helo=shadovitzcmptr) by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AWUGM-0004PZ-00; Tue, 16 Dec 2003 21:30:22 -0800 Received: by localhost with Microsoft MAPI; Tue, 16 Dec 2003 20:45:44 -0800 Message-ID: <01C3C415.9359D080.david@shadovitz.com> From: David Shadovitz Reply-To: "david@shadovitz.com" To: 'Neil Conway' Cc: "pgsql-performance@postgresql.org" Subject: Re: Why is VACUUM ANALYZE so slow? Date: Tue, 16 Dec 2003 20:37:02 -0800 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/249 X-Sequence-Number: 5109 Neil, Thanks for the good advice. I noticed that I had some sessions for which I could not account, and I think even a 2nd postmaster running. It looks like I've cleaned everything up, and now I can VACUUM and I can DROP an index which wouldn't drop. And I'm looking into upgrading PostgreSQL. -David On Tuesday, December 16, 2003 2:51 PM, Neil Conway [SMTP:neilc@samurai.com] wrote: > "David Shadovitz" writes: > > I'm running PG 7.2.2 on RH Linux 8.0. > > Note that this version of PostgreSQL is quite old. > > > I'd like to know why "VACUUM ANALYZE
" is extemely slow (hours) for > > certain tables. > > Is there another concurrent transaction that has modified the table > but has not committed? VACUUM ANALYZE will need to block waiting for > it. You might be able to get some insight into this by examining the > pg_locks system view: > > http://www.postgresql.org/docs/current/static/monitoring-locks.html > > As well as the pg_stat_activity view. > > -Neil