In an interesting epilogue to this thread, I just encountered
something unusual.
Since having disabled autovacuum in the cluster in which it was
preventing dropdb from working (because autovacuum the autovacuum
daemon was behaving as a user accessing the database), dropdb has
been working fine.
Yesterday, though, I created a new cluster to house an on-line backup
from a production server. The new cluster includes a postgresql.conf
from the production server in which autovacuum was enabled. From the
logs of the new cluster, autovacuum began processing as soon as the
on-line backup recovery process was complete.
Then, last night, my dropdb failed for the first time since having
disabled it in my original postgres cluster on this server with a
warning that users were accessing the database.
Is it possible for an autovacuum daemon in a given cluster to have an
impact on all postgres clusters running on a server?
--
Thomas F. O'Connell
Database Architecture and Programming
Co-Founder
Sitening, LLC
http://www.sitening.com/
3004 B Poston Avenue
Nashville, TN 37203-1314
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)
