Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Ye olde drop-the-database-you-just-left problem
- From: Gregory Stark <stark(at)enterprisedb(dot)com>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: <pgsql-hackers(at)postgreSQL(dot)org>
- Subject: Re: Ye olde drop-the-database-you-just-left problem
- Date: Wed, 30 May 2007 20:59:06 +0100
- Message-id: <87wsyqhylx.fsf@oxford.xeocode.com> <text/plain>
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)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
- Follow-Ups:
- Re: Ye olde drop-the-database-you-just-left problem
- From: Tom Lane
- Re: Ye olde drop-the-database-you-just-left problem
- References:
- Ye olde drop-the-database-you-just-left problem
- From: Tom Lane
- Ye olde drop-the-database-you-just-left problem
- Prev by Date: Re: libedit-preferred by default
- Next by Date: Re: Padding on 64-bit
- Previous by thread: Re: Ye olde drop-the-database-you-just-left problem
- Next by thread: Re: Ye olde drop-the-database-you-just-left problem
- Indexes: