wsheldah@lexmark.com writes:
> If vacuum in 7.2 skips tables it can't lock,
It does not.
The real change in 7.2 is that vacuum requires only an ordinary writer's
lock on the table, not exclusive lock. Since a write lock doesn't
conflict with read or write locks (basically it only conflicts with
schema-changing operations) we expect that vacuum will run concurrently
with most ordinary database operations.
regards, tom lane
