Commit514d4a1

committed

Remove INCLUDE attributes section from docs.

Discussing covering indexes in a chapter that is mostly about thebehavior of B-Tree operator classes is unnecessary. The CREATE INDEXdocumentation's handling of covering indexes seems sufficient.Discussion:https://postgr.es/m/CAH2-WzmpU=L_6VjhhOAMfoyHLr-pZd1kDc+jpa3c3a8EOmtcXA@mail.gmail.com

1 parente716585 commit514d4a1Copy full SHA for 514d4a1

File tree

-17

lines changed

-17

lines changed

Lines changed: 0 additions & 17 deletions

Original file line number	Diff line number	Diff line change
`@@ -433,23 +433,6 @@ returns bool`
`433`	`433`
`434`	`434`	`</sect1>`
`435`	`435`
`436`		`-<sect1 id="btree-included-attributes">`
`437`		`- <title>Included attributes in B-tree indexes</title>`
`438`		`-`
`439`		`- <para>`
`440`		`- As of <productname>PostgreSQL</productname> 11.0 there is an optional`
`441`		`- INCLUDE clause, which allows to add non-key (included) attributes to index.`
`442`		`- Those included attributes allow more queries to benefit from index-only scans.`
`443`		`- We never use included attributes in ScanKeys for search. That allows us to`
`444`		`- include into B-tree any datatypes, even those which don't have suitable`
`445`		`- operator classes. Included columns only stored in regular tuples on leaf`
`446`		`- pages. All pivot tuples on non-leaf pages and highkey tuples are truncated`
`447`		`- to contain only key attributes. That helps to slightly reduce the size of`
`448`		`- index.`
`449`		`- </para>`
`450`		`-`
`451`		`-</sect1>`
`452`		`-`
`453`	`436`	`<sect1 id="btree-implementation">`
`454`	`437`	`<title>Implementation</title>`
`455`	`438`

Comments

(0)