From: "Trewern, Ben" <Ben.Trewern@mowlem.com>
> If there is a transaction running when 'vacuumdb -a -z' is run (as a cron
> job) it stops running at that database till the transaction completes.
That
> is not so much of a problem until a new client tries to connect to the
> database. This new connection hangs, waiting for the vacuum to complete.
> This situation is not all that helpful and means I have to be careful at
> what time I run vacuum so it does not interfere with new clients. Is this
a
> bug or the standard way in which postgres works and are there any plans
> change this?
Would vacuuming the tables one at a time not help here? It'd mean a small
script to read a list of databases/tables out of PG but should reduce the
impact on your clients (if I'm thinking straight here)
- Richard Huxton