On May 31, 2007, at 1:32 AM, Zeugswetter Andreas ADI SD wrote:
 However, it suddenly struck me that we could
probably make most of the problem go away if we put that same wait
DROP DATABASE itself --- that is, if we see other backends in the
target DB, sleep for a second or two and then recheck before erroring

Yup, waiting in drop database up to 10-30 secs would imho be fine.

Even 10 seconds seems rather long, doesn't it? You'd have to have an awfully busy system to need to wait more than like 5 seconds for the closing backend to get scheduled, and it'd be rather ugly to force someone to wait 30 seconds just to find out that someone's still connected to the database.

How about starting with 5 seconds and seeing if that takes care of most situations?
Jim Nasby                                            [EMAIL PROTECTED]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to