Does this mean it could be any transaction, even one that has not done
anything with large objects, but one that started prior to the large objects
being deleted?
All access to the DB is done via JDBC, so has this JDBC issue been fixed in
7.4.5?
Chris
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Friday, April 01, 2005 1:07 PM
To: cjwhite@cisco.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Help understanding VACUUM info on 7.4.5
"Chris White (cjwhite)" <cjwhite@cisco.com> writes:
> Below I have info which shows a DB which has had all objects deleted
> and then vacuumed. As can been seen it say it has "9014 dead rows that
> can't been removed". What does that mean?
That means there's an open transaction that is old enough to be able to see
those rows under MVCC rules, so VACUUM dare not remove them.
Check for clients that are issuing a BEGIN and then sitting with the
transaction open. Older versions of JDBC did that behind your back, IIRC.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster