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

diff --git a/doc/src/sgml/btree.sgml b/doc/src/sgml/btree.sgml
index 336d026ea16032bcb41581d1f4c09bcdb6b0d866..8bd0badb28090283e612e0516de10c43342dd2d3 100644 (file)
--- a/doc/src/sgml/btree.sgml
+++ b/doc/src/sgml/btree.sgml
@@ -433,23 +433,6 @@ returns bool
 
 
 
-
- Included attributes in B-tree indexes
-
- 
-  As of PostgreSQL 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.
- 
-
-
-
 
  Implementation