diff options
| author | Robert Haas <rhaas@postgresql.org> | 2016-08-23 10:05:13 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2016-08-23 10:05:13 -0400 |
| commit | ff36700c3ba2180047b4103de440ffaa34889b72 (patch) | |
| tree | 38be44401a2842764af192b18aac0bcb0f167120 | |
| parent | 7b405b3e04779fc0a026c9c6ac3e06194948b253 (diff) | |
| download | postgresql-ff36700c3ba2180047b4103de440ffaa34889b72.tar.gz postgresql-ff36700c3ba2180047b4103de440ffaa34889b72.zip | |
Remove duplicate word from comment.
Erik Rijkers
| -rw-r--r-- | src/backend/storage/lmgr/lmgr.c | 2 |
1 files changed, 1 insertions, 1 deletions
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 |