Thanks, for the input.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Friday, April 01, 2005 1:49 PM
To: [EMAIL PROTECTED]
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Help understanding VACUUM info on 7.4.5
"Chris
"Chris White \(cjwhite\)" <[EMAIL PROTECTED]> writes:
> 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?
Exactly.
> All access to the DB is done via JDBC, so has this JDBC issue b
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Friday, April 01, 2005 1:07 PM
To: [EMAIL PROTECTED]
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Help understanding VACUUM info on 7.4.5
"Chris White (cjwhite)" <[EMAIL PROTECTED]> writes:
> Below I have in
"Chris White (cjwhite)" <[EMAIL PROTECTED]> 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
Hi,
I am running
Postgres 7.4.5 and am storing binary objects in the largeobject table. We want
to keep the size of the database and especially the large object table to a
minimum, so we vacuum it (not full) on a regular basis. However, what we have
seen is that even after deleting entries
