Kim <kim@myemma.com> writes:
> Running a vac on an 8.2 client connecting to an 8.2 database (following
> example was for a 14 row static table) - vacuums will sit (for lack of a
> better word) for anywhere from ten to twenty minutes before taking a
> lock out on the table and doing work there.
How big is this database (how many pg_class entries)? What do you get
from "VACUUM VERBOSE pg_class"? The truss results make it sound like
the problem is pgstat_vacuum_tabstat() taking a long time, but that code
has not changed since 8.1 ...
regards, tom lane
