diff options
| author | Michael Paquier | 2021-09-29 02:56:13 +0000 |
|---|---|---|
| committer | Michael Paquier | 2021-09-29 02:56:13 +0000 |
| commit | c8dd2cb49405d2a39a714bd5adc31d39b8372a4e (patch) | |
| tree | 6d6da40c3a59ed56aea2e9d67ed41baa540063ec /doc/src/sgml/btree.sgml | |
| parent | 5b0b699f748ead1b7414c58aaa7cf0ea83808147 (diff) | |
doc: Fix some typos and markups
Author: Ekaterina Kiryanova
Discussion: https://postgr.es/m/[email protected]
Backpatch-through: 14
Diffstat (limited to 'doc/src/sgml/btree.sgml')
| -rw-r--r-- | doc/src/sgml/btree.sgml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/btree.sgml b/doc/src/sgml/btree.sgml index f569f93f352..a9200ee52e6 100644 --- a/doc/src/sgml/btree.sgml +++ b/doc/src/sgml/btree.sgml @@ -664,7 +664,7 @@ options(<replaceable>relopts</replaceable> <type>local_relopts *</type>) returns certain implementation-level heuristics will fail to identify and delete even one garbage index tuple (in which case a page split or deduplication pass resolves the issue of an incoming new tuple not - fitting on a leaf page). The worst case number of versions that + fitting on a leaf page). The worst-case number of versions that any index scan must traverse (for any single logical row) is an important contributor to overall system responsiveness and throughput. A bottom-up index deletion pass targets suspected @@ -706,7 +706,7 @@ options(<replaceable>relopts</replaceable> <type>local_relopts *</type>) returns This is expected with any B-Tree index that is subject to significant version churn from <command>UPDATE</command>s that rarely or never logically modify the columns that the index covers. - The average and worst case number of versions per logical row can + The average and worst-case number of versions per logical row can be kept low purely through targeted incremental deletion passes. It's quite possible that the on-disk size of certain indexes will never increase by even one single page/block despite @@ -811,7 +811,7 @@ options(<replaceable>relopts</replaceable> <type>local_relopts *</type>) returns constraints) to use deduplication. This allows leaf pages to temporarily <quote>absorb</quote> extra version churn duplicates. Deduplication in unique indexes augments bottom-up index deletion, - especially in cases where a long-running transactions holds a + especially in cases where a long-running transaction holds a snapshot that blocks garbage collection. The goal is to buy time for the bottom-up index deletion strategy to become effective again. Delaying page splits until a single long-running |