Hi,
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).
Background Info:
I observed some performance problems our database seemed
to be using an unusually
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
Hi all
I have had this issue a couple of times now. on Solaris, and on 7.3 of the db.
I was did a normal vacuum and then I did a full which hung on a table, I waited for
over an hour but there were no activity going on so I ctrl'cd the job in a terminal
window, kill off all associated
