We're seeing similar behaviour on several of our FreeBSD servers too.
It doesn't look like open files, or filesystem snapshots. Rebooting
does reset it, but restarting PG makes no difference.
We've got an assortment of different versions of both FreeBSD and
PostgreSQL, some of which are demonstrat
Um, whaddya mean "dumpall was getting stuck behind vacuum's lock"?
A plain vacuum doesn't take any locks that would block pg_dump.
Dammit, just looked and the setup I originally encountered the problem
on and tracked it down to the vacuum process, and it is indeed set up
to perform a full vacuum
