<title>Built-in Operator Classes</title>
<para>
- The core <productname>PostgreSQL</productname> distribution includes
+ The core <productname>PostgreSQL</productname> distribution
includes the <acronym>BRIN</acronym> operator classes shown in
<xref linkend="brin-builtin-opclasses-table">.
</para>
<para>
<productname>PostgreSQL</productname> provides the index methods
- B-tree, hash, GiST, SP-GiST, and GIN. Users can also define their own index
- methods, but that is fairly complicated.
+ B-tree, hash, GiST, SP-GiST, GIN, and BRIN. Users can also define their own
+ index methods, but that is fairly complicated.
</para>
<para>
<para>
The name of the index method to be used. Choices are
<literal>btree</literal>, <literal>hash</literal>,
- <literal>gist</literal>, <literal>spgist</> and <literal>gin</>.
+ <literal>gist</literal>, <literal>spgist</>, <literal>gin</>, and
+ <literal>brin</>.
The default method is <literal>btree</literal>.
</para>
</listitem>
</caution>
<para>
- Currently, only the B-tree, GiST and GIN index methods support
+ Currently, only the B-tree, GiST, GIN, and BRIN index methods support
multicolumn indexes. Up to 32 fields can be specified by default.
(This limit can be altered when building
<productname>PostgreSQL</productname>.) Only B-tree currently
hasn't yet been summarized. Those insertions do not create a new index
entry; instead, the page range remains unsummarized until later.
-Wehn VACUUM is run on the table, all unsummarized page ranges are
+Whenever VACUUM is run on the table, all unsummarized page ranges are
summarized. This action can also be invoked by the user via
brin_summarize_new_values(). Both these procedures scan all the
unsummarized ranges, and create a summary tuple. Again, this includes the