aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2018-06-16 15:28:50 -0700
committerPeter Geoghegan <pg@bowt.ie>2018-06-16 15:28:50 -0700
commit514d4a1338d5409431d644eaf453193ac362ef16 (patch)
tree310d4adf32cef7e71f76d1d48cded2c6d61a2f53
parente716585235b175de767d3b210f0a963457dfa77f (diff)
downloadpostgresql-514d4a1338d5409431d644eaf453193ac362ef16.tar.gz
postgresql-514d4a1338d5409431d644eaf453193ac362ef16.zip
Remove INCLUDE attributes section from docs.
Discussing covering indexes in a chapter that is mostly about the behavior of B-Tree operator classes is unnecessary. The CREATE INDEX documentation's handling of covering indexes seems sufficient. Discussion: https://postgr.es/m/CAH2-WzmpU=L_6VjhhOAMfoyHLr-pZd1kDc+jpa3c3a8EOmtcXA@mail.gmail.com
-rw-r--r--doc/src/sgml/btree.sgml17
1 files changed, 0 insertions, 17 deletions
diff --git a/doc/src/sgml/btree.sgml b/doc/src/sgml/btree.sgml
index 336d026ea16..8bd0badb280 100644
--- a/doc/src/sgml/btree.sgml
+++ b/doc/src/sgml/btree.sgml
@@ -433,23 +433,6 @@ returns bool
</sect1>
-<sect1 id="btree-included-attributes">
- <title>Included attributes in B-tree indexes</title>
-
- <para>
- As of <productname>PostgreSQL</productname> 11.0 there is an optional
- INCLUDE clause, which allows to add non-key (included) attributes to index.
- Those included attributes allow more queries to benefit from index-only scans.
- We never use included attributes in ScanKeys for search. That allows us to
- include into B-tree any datatypes, even those which don't have suitable
- operator classes. Included columns only stored in regular tuples on leaf
- pages. All pivot tuples on non-leaf pages and highkey tuples are truncated
- to contain only key attributes. That helps to slightly reduce the size of
- index.
- </para>
-
-</sect1>
-
<sect1 id="btree-implementation">
<title>Implementation</title>