This is a discussion on Re: Refactoring lock.c within the Pgsql Patches forums, part of the PostgreSQL category; --> On Wed, 2005-02-02 at 21:41 +0200, Heikki Linnakangas wrote: > There's two almost identical pieces of code in LockRelease ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Wed, 2005-02-02 at 21:41 +0200, Heikki Linnakangas wrote: > There's two almost identical pieces of code in LockRelease and > LockReleaseAll that do the opposite of GrantLock. > > Here's a small patch that replaces those pieces with a static UnGrantLock > function. LockReleaseAll() did not update the holdMask bits for a released proclock, but it will do so now. That's okay because we're removing the proclock, right? Barring any objections, I'll apply this to HEAD today or tomorrow. -Neil ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org |
| ||||
| On Thu, 3 Feb 2005, Neil Conway wrote: > On Wed, 2005-02-02 at 21:41 +0200, Heikki Linnakangas wrote: >> There's two almost identical pieces of code in LockRelease and >> LockReleaseAll that do the opposite of GrantLock. >> >> Here's a small patch that replaces those pieces with a static UnGrantLock >> function. > > LockReleaseAll() did not update the holdMask bits for a released > proclock, but it will do so now. That's okay because we're removing the > proclock, right? Right. - Heikki ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| Thread Tools | |
| Display Modes | |
|
|