summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Haas2011-08-22 16:16:03 +0000
committerRobert Haas2011-08-22 16:16:27 +0000
commit7488936478cbe2de19a94cb9fbde78e6cd6db947 (patch)
treef8bac1f3f65f2638fb3aeeb78b279aff89603e33
parent660a081c3f6892dae353136fa0883cd3c69813d4 (diff)
Typo fix.
-rw-r--r--src/backend/storage/lmgr/lock.c2
1 files changed, 1 insertions, 1 deletions
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