Skip to content

Commit 80b986c

Browse files
committed
Mention BRIN as able to do multi-column indexes
Documentation mentioned B-tree, GiST and GIN as able to do multicolumn indexes; I failed to add BRIN to the list. Author: Petr Jediný Reviewed-By: Fujii Masao, Emre Hasegeli
1 parent 1f4e9da commit 80b986c

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

doc/src/sgml/indices.sgml

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -395,7 +395,8 @@ CREATE INDEX test2_mm_idx ON test2 (major, minor);
395395
</para>
396396

397397
<para>
398-
Currently, only the B-tree, GiST and GIN index types support multicolumn
398+
Currently, only the B-tree, GiST, GIN, and BRIN
399+
index types support multicolumn
399400
indexes. Up to 32 columns can be specified. (This limit can be
400401
altered when building <productname>PostgreSQL</productname>; see the
401402
file <filename>pg_config_manual.h</filename>.)
@@ -440,6 +441,15 @@ CREATE INDEX test2_mm_idx ON test2 (major, minor);
440441
the query conditions use.
441442
</para>
442443

444+
<para>
445+
A multicolumn BRIN index can be used with query conditions that
446+
involve any subset of the index's columns. Like GIN and unlike B-tree or
447+
GiST, index search effectiveness is the same regardless of which index
448+
column(s) the query conditions use. The only reason to have multiple BRIN
449+
indexes instead of one multicolumn BRIN index on a single table is to have
450+
a different <literal>pages_per_range</literal> storage parameter.
451+
</para>
452+
443453
<para>
444454
Of course, each column must be used with operators appropriate to the index
445455
type; clauses that involve other operators will not be considered.

0 commit comments

Comments
 (0)