Alvaro Herrera wrote:
> On Mon, Dec 20, 2004 at 03:09:31PM -0500, Tom Lane wrote:
> > Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> > > Here is the LockObject patch I was able to come up with. It's almost
> > > the same patch that Rod Taylor published two years ago; basically, it
> > > expands LOCKTAG with a ClassId attribute, and provides a LockObject
> > > method to allow locking arbitrary objects.
> > I wonder whether it wouldn't be possible to clean up the "XactLockTable"
> > kluge with this --- ie, instead of denoting transaction locks by a
> > special relation ID, denote them by a special class ID. That might just
> > move the kluginess from one place to another, but it's worth thinking about.
> How about locking the special class InvalidOid? We don't use that ATM
When we roll over OID's do we make sure we never return InvalidOid?
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
In response to
pgsql-patches by date
|Next:||From: Alvaro Herrera||Date: 2004-12-20 20:55:44|
|Subject: Re: LockObject patch|
|Previous:||From: Guillaume LELARGE||Date: 2004-12-20 20:49:07|
|Subject: Update for french pg_resetxlog.po file|