Skip site navigation (1) Skip section navigation (2)

Re: Ye olde drop-the-database-you-just-left problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Ye olde drop-the-database-you-just-left problem
Date: 2007-06-01 19:41:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> Even if we had a semaphore of the sort you suggest, I doubt people would
>> want DROP DATABASE to wait indefinitely.  The real question here is how
>> long is it reasonable for DROP DATABASE to wait before failing ...

> 10 to 15 seconds, I'd say.  Is that going to be long enough for backends to 
> release, assuming the DB isn't under extreme load?

While testing this, 10 seconds seemed too long --- more than long enough
for someone to start thinking it's broken.  I settled on 5 seconds which
seemed about the edge of the threshold of pain.  Our experience with the
buildfarm suggests that 1 second is usually long enough (since that's
the delay we were using in the contrib regression tests, and they don't
fail often on this), so I think it'll be all right at 5.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2007-06-01 19:54:54
Subject: Re: Do we need a TODO? (was Re: Concurrently updatinganupdatable view)
Previous:From: Bruce MomjianDate: 2007-06-01 19:33:04
Subject: Re: [PATCHES] xml2 contrib patch supporting default XML namespaces

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group