> Please search this message in the archives:
right. heh. Well, moving on...
> Since subids and offnums are only 16 bits, we could pack all of these
> cases into 64 bits with a 16-bit type identifier to distinguish the
> cases. That would mean that LOCKTAG doesn't get any bigger than it is
> now, and we'd have plenty of room for expansion still with more types.
Ok, this makes perfect sense, kind of what I was saying only better.
The only thing I can add to it at this point is to reorganize the lock
view(s) correspondingly...should be 1 view for each specific lock type
plus 1 generic one for all locks. A new datum for the generic lock
type (plus some casts) might be worth considering.
Is it possible for one backend (with superuser privs) to release a lock
held by anotether?
pgsql-hackers by date
|Next:||From: Oleg Bartunov||Date: 2005-01-25 20:21:30|
|Previous:||From: Merlin Moncure||Date: 2005-01-25 20:02:45|
|Subject: Re: userlock changes for 8.1/8.2 |
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2005-01-25 21:22:25|
|Subject: Re: [HACKERS] userlock changes for 8.1/8.2 |
|Previous:||From: Kris Jurka||Date: 2005-01-25 17:47:56|
|Subject: Re: add soundex difference function to contrib/fuzzystrmatch|