Eamonn Kent wrote:
I am using PostgreSQL 8.1.4 for an embedded application. For some
reason, vacuum is not able to identify rows that are candidates for
removal (i.e., mark space as available).
[snip]
If I shutdown our application and run a vacuum full, the space is
recovered and the databa
"Mark M. Huber" <[EMAIL PROTECTED]> writes:
> I was did a normal vacuum and then I did a full which hung on a table,
Sounds to me like some other transaction is holding a lock on that
table.
In recent releases you can look in the pg_locks system view to see
who's got the lock.
