From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: [PATCHES] Lock |
Date: | 1999-12-20 02:15:28 |
Message-ID: | 199912200215.VAA19562@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
> 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 ...
Yep, I figured it would be weird to get working.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-12-20 02:17:00 | Re: initdb.sh fixed |
Previous Message | Peter Eisentraut | 1999-12-20 00:18:58 | Re: [HACKERS] psql compile errors |