From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nolan Cafferky <Nolan.Cafferky@rbsinteractive.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Problems with VACUUM and "dead row versions cannot be removed yet"
Date: Wed, 18 Oct 2006 13:59:59 -0400
Message-ID: <28531.1161194399@sss.pgh.pa.us> (raw)
In-Reply-To: <45366394.3090806@rbsinteractive.com>
References: <45366394.3090806@rbsinteractive.com>
Nolan Cafferky <Nolan.Cafferky@rbsinteractive.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Nolan.Cafferky@rbsinteractive.com
Subject: Re: Problems with VACUUM and "dead row versions cannot be removed yet"
In-Reply-To: <28531.1161194399@sss.pgh.pa.us>
References: <45366394.3090806@rbsinteractive.com> <28531.1161194399@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox