diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2015-04-13 14:28:21 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2015-04-13 14:28:21 -0300 |
| commit | b5213e14a4759b8f6817359c827950bae5452136 (patch) | |
| tree | 54a71d3f370e4f259b40b56d63fb939586512cfb /src | |
| parent | 81134af3ec09d67043833f8d614fd688f17cb213 (diff) | |
| download | postgresql-b5213e14a4759b8f6817359c827950bae5452136.tar.gz postgresql-b5213e14a4759b8f6817359c827950bae5452136.zip | |
Remove duplicated word in README
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/access/nbtree/README | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/nbtree/README b/src/backend/access/nbtree/README index c904d2ff6c8..5c0bc794848 100644 --- a/src/backend/access/nbtree/README +++ b/src/backend/access/nbtree/README @@ -178,7 +178,7 @@ rather somewhere to the right of that page. To ensure that VACUUM can't prematurely remove such heap tuples, we require btbulkdelete to obtain a super-exclusive lock on every leaf page in the index, even pages that don't contain any deletable tuples. Any scan which could yield incorrect -results if the tuple at a TID matching the the scan's range and filter +results if the tuple at a TID matching the scan's range and filter conditions were replaced by a different tuple while the scan is in progress must hold the pin on each index page until all index entries read from the page have been processed. This guarantees that the btbulkdelete |