aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>1999-04-30 17:03:04 +0000
committerBruce Momjian <bruce@momjian.us>1999-04-30 17:03:04 +0000
commit099164039dae2fec176d7b605b128592ac4b02a3 (patch)
treea6b2db29c907cd7c6255923f91ed9fda0c4f9822
parentf4dcafc825032ae0b9ff39f912bc274bbdc2fd02 (diff)
downloadpostgresql-099164039dae2fec176d7b605b128592ac4b02a3.tar.gz
postgresql-099164039dae2fec176d7b605b128592ac4b02a3.zip
cleanup
-rw-r--r--src/backend/storage/lmgr/lock.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/storage/lmgr/lock.c b/src/backend/storage/lmgr/lock.c
index 9ed7fca8786..c39138ff129 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.48 1999/04/30 16:22:46 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/storage/lmgr/lock.c,v 1.49 1999/04/30 17:03:04 momjian Exp $
*
* NOTES
* Outside modules can create a lock table and acquire/release
@@ -819,7 +819,7 @@ LockResolveConflicts(LOCKMETHOD lockmethod,
{
/* ------------------------
* If someone with a greater priority is waiting for the lock,
- * do not continue and share the lock, even if we can. bjm
+ * do not continue and share the lock, even if we can.
* Don't do this if the process already has some locks, because
* this could hold up other people waiting on our locks, causing
* a priority inversion. bjm