Re: [PATCHES] Lock - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCHES] Lock
Date
Msg-id Pine.LNX.4.21.9912190124040.356-100000@localhost.localdomain
Whole thread Raw
Responses Re: [HACKERS] Re: [PATCHES] Lock
List pgsql-hackers
On 1999-12-18, Bruce Momjian mentioned:

> > * Allow LOCK TABLE tab1, tab2, tab3 so all tables locked in unison

> It took a few minutes, but I remember the use for this.  If you are
> going to hang waiting to lock tab3, you don't want to lock tab1 and tab2
> while you are waiting for tab3 lock.  The user wanted all tables to lock
> in one operation without holding locks while waiting to complete all
> locking.
> 
> Can you do the locks, and if one fails, not hang, but unlock the
> previous tables, go lock/hang on the failure, and go back and lock the
> others? Seems it would have to be some kind of lock/fail/unlock/wait
> loop.

That's what I suspected. But of course LockRelation() doesn't return
anything based on whether it succeeded, it just hangs, so it'll take a
little more work. Next year ...

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pgindent (Re: [HACKERS] LONG varsize - how to go on)t
Next
From: Peter Eisentraut
Date:
Subject: Re: initdb.sh fixed