From 7488936478cbe2de19a94cb9fbde78e6cd6db947 Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Mon, 22 Aug 2011 12:16:03 -0400
Subject: [PATCH] Typo fix.

---
 src/backend/storage/lmgr/lock.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/storage/lmgr/lock.c b/src/backend/storage/lmgr/lock.c
index 05efafc0b06..1787cbccb79 100644
--- a/src/backend/storage/lmgr/lock.c
+++ b/src/backend/storage/lmgr/lock.c
@@ -3309,7 +3309,7 @@ DumpAllLocks(void)
  *
  * When switching from Hot Standby mode to normal operation, the locks will
  * be already held by the startup process. The locks are acquired for the new
- * procs without checking for conflicts, so we don'get a conflict between the
+ * procs without checking for conflicts, so we don't get a conflict between the
  * startup process and the dummy procs, even though we will momentarily have
  * a situation where two procs are holding the same AccessExclusiveLock,
  * which isn't normally possible because the conflict. If we're in standby
-- 
GitLab