On Mon, Dec 20, 2004 at 03:09:31PM -0500, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> 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
AFAICS.

Anything else would require having a special relation registered, which
is where we are now ...

-- 
Alvaro Herrera (<[EMAIL PROTECTED]>)
"La rebeldía es la virtud original del hombre" (Arthur Schopenhauer)

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to