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: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
- To: "Brian Hurt" <bhurt(at)janestcapital(dot)com>, "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: Thu, 31 May 2007 10:32:18 +0200
- Message-id: <E1539E0ED7043848906A8FF995BDA579021B2C35@m0143.s-mxs.net> <text/plain>
> > 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. Yup, waiting in drop database up to 10-30 secs would imho be fine. Andreas
- References:
- Ye olde drop-the-database-you-just-left problem
- From: Tom Lane
- Re: Ye olde drop-the-database-you-just-left problem
- From: Brian Hurt
- Ye olde drop-the-database-you-just-left problem
- Prev by Date: Re: ERROR: index row size 2960 exceeds btree maximum
- Next by Date: Re: TOAST usage setting
- 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: