Re: postgresql locks the whole table!

Jeff Davis wrote:
> The way I understand it, is that you're having trouble storing all of
> the xids in the row; right now you just store one and mark it "locked".
> If you were able to store several, but not necessarily all xids in all
> cases, wouldn't that be a big improvement? The xids not in the list
> would lock, as they do now, and the ones in the list would show an
> improvement by sharing the lock, right?
>
> Otherwise I don't entirely understand what you're saying.

Yes, we could do that but we really want something that isn't going to
work only some of the time. Ideally we want something that can share no
matter how many backends try.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073