On Mar 11, 2006, at 4:13 PM, Tom Lane wrote:
For a "real" solution, perhaps DROP DATABASE could somehow look to determine if there's an autovac daemon active in the target database, and if so send it a SIGINT and wait for it to go away.
In general, it also seems like a --force option or something similar would be reasonable for dropdb because the state of the database in terms of user activity wouldn't seem to matter a whole lot if the intent is to drop it.
-- 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)