Re: Revised Patch to allow multiple table locks in "Unison"

> Bruce Momjian wrote:
> > 
> > The unusual case here is that deadlock is not checked on request, but
> > only after waiting on the lock for a while.  This is because deadlock
> > detection is an expensive operation.  
> 
> But that is what happens.  If one of the locks is not obtained, the
> algorithm does wait on that lock (after releasing the other locks).
> In the case of a deadlock (tom's scenario #1) it would wait forever,
> but the deadlock detection will find it in there and break it.

OK, I thought you were talking about the LOCK a,b case, not the other
case where we had a previous LOCK statement.  Sorry.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026