From b686927f4b980beb3f6cce47cab0625f5cdb586d Mon Sep 17 00:00:00 2001
From: "Marc G. Fournier" <scrappy@hub.org>
Date: Fri, 28 Aug 1998 12:08:03 +0000
Subject: [PATCH] From: Massimo Dal Zotto <dz@cs.unitn.it>

I have this small patch which fixes a typo in my previous lock patches.
Fortunately the bug affects only user locks.

-
---
 src/backend/storage/lmgr/lock.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/backend/storage/lmgr/lock.c b/src/backend/storage/lmgr/lock.c
index b35008a3bb8..52ddd635832 100644
--- a/src/backend/storage/lmgr/lock.c
+++ b/src/backend/storage/lmgr/lock.c
@@ -7,7 +7,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/storage/lmgr/lock.c,v 1.33 1998/08/25 21:20:26 scrappy Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/storage/lmgr/lock.c,v 1.34 1998/08/28 12:08:03 scrappy Exp $
  *
  * NOTES
  *	  Outside modules can create a lock table and acquire/release
@@ -668,7 +668,7 @@ LockAcquire(LOCKMETHOD lockmethod, LOCKTAG *locktag, LOCKMODE lockmode)
 			{
 				SHMQueueDelete(&result->queue);
 				result = (XIDLookupEnt *) hash_search(xidTable,
-													  (Pointer) &result,
+													  (Pointer) result,
 													  HASH_REMOVE, &found);
 				if (!result || !found) {
 					elog(NOTICE, "LockAcquire: remove xid, table corrupted");