From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Neil Padgett <npadgett(at)redhat(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Patch to allow multiple table locks in "Unison" |
Date: | 2001-07-25 22:41:11 |
Message-ID: | 200107252241.f6PMfBv19546@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
> In short, the order has to be user-specified, which pretty much
> means it had better be as given in the statement. Which raises
> the significant question of why bother with such a patch at all, as
> opposed to using a series of LOCK statements as one can do already.
> (With more flexibility, since separate LOCK statements can specify
> different lock modes.) What's the rationale for adding such a
> feature in the first place? I don't see that it's buying anything.
The advantage is that you don't hold lock A while waiting for lock B.
It gets all the locks at the same time.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(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 | Neil Padgett | 2001-07-25 22:59:12 | Re: Patch to allow multiple table locks in "Unison" |
Previous Message | Tom Lane | 2001-07-25 07:17:01 | Re: Patch to allow multiple table locks in "Unison" |