Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id DAEB19FA4AD for ; Wed, 18 Oct 2006 15:00:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 74244-05 for ; Wed, 18 Oct 2006 15:00:02 -0300 (ADT) 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 5DAE89F9FAC for ; Wed, 18 Oct 2006 15:00:02 -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 k9IHxx4W028532; Wed, 18 Oct 2006 13:59:59 -0400 (EDT) To: Nolan Cafferky cc: pgsql-admin@postgresql.org Subject: Re: Problems with VACUUM and "dead row versions cannot be removed yet" In-reply-to: <45366394.3090806@rbsinteractive.com> References: <45366394.3090806@rbsinteractive.com> Comments: In-reply-to Nolan Cafferky message dated "Wed, 18 Oct 2006 10:25:40 -0700" Date: Wed, 18 Oct 2006 13:59:59 -0400 Message-ID: <28531.1161194399@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.088 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200610/112 X-Sequence-Number: 23415 Nolan Cafferky writes: > I've got an admin_sessions table on a postgres 8.0.8 server that gets > updated frequently, with about 30 live rows at any given time. We > VACUUM the table nightly, which has served us with no problems for quite > some time. Well, this morning we noticed some seriously slow queries > against the table, and VACUUM VERBOSE reported around 84,000 rows that > were "nonremovable". Same results with VACUUM FULL ANALYZE VERBOSE. Lots of nonremovable rows means you've got some really old open transactions. Look into pg_stat_activity or pg_locks to help find the culprit. regards, tom lane