"Tom Lane" <tgl@sss.pgh.pa.us> writes:
> However, it suddenly struck me that we could probably make most of the
> problem go away if we put that same wait into 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 out.
Is there any way to tell, perhaps from the command string, that the process is
about to start exiting? What stage of exiting is it that we think the kernel
goes to lunch?
-- Gregory Stark EnterpriseDB http://www.enterprisedb.com
