postgres.git / summary / log / commit / refs

commit    ff36700c3ba2180047b4103de440ffaa34889b72
Author:   Robert Haas <rhaas@postgresql.org>
Date:     Tue Aug 23 14:05:13 2016 +0000
First released in: 10.0

    Remove duplicate word from comment.
    
    Erik Rijkers


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

diff --git a/src/backend/storage/lmgr/lmgr.c b/src/backend/storage/lmgr/lmgr.c
index eeedc38251a..cbee20e9bf7 100644
--- a/src/backend/storage/lmgr/lmgr.c
+++ b/src/backend/storage/lmgr/lmgr.c
@@ -33,7 +33,7 @@
  * constraint violations.  It's theoretically possible that a backend sees a
  * tuple that was speculatively inserted by another backend, but before it has
  * started waiting on the token, the other backend completes its insertion,
- * and then then performs 2^32 unrelated insertions.  And after all that, the
+ * and then performs 2^32 unrelated insertions.  And after all that, the
  * first backend finally calls SpeculativeInsertionLockAcquire(), with the
  * intention of waiting for the first insertion to complete, but ends up
  * waiting for the latest unrelated insertion instead.  Even then, nothing


[parent: 7b405b3e0477]