Skip site navigation (1) Skip section navigation (2)

Re: LockObject patch

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: LockObject patch
Date: 2004-12-20 20:48:00
Message-ID: 20041220204800.GA5287@dcc.uchile.cl (view raw or flat)
Thread:
Lists: pgsql-patches
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
AFAICS.

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

-- 
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"La rebeldía es la virtud original del hombre" (Arthur Schopenhauer)

In response to

Responses

pgsql-patches by date

Next:From: Guillaume LELARGEDate: 2004-12-20 20:49:07
Subject: Update for french pg_resetxlog.po file
Previous:From: Tom LaneDate: 2004-12-20 20:09:31
Subject: Re: LockObject patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group