doc: mention "bloom" as a possible index access method

Also remove USING erroneously added recently.

Reported-by: Jeff Janes

Discussion: https://postgr.es/m/CAMkU=1zhCpC7hottyMWM5Pimr9vRLprSwzLg+7PgajWhKZqRzw@mail.gmail.com

Backpatch-through: 10
This commit is contained in:
Bruce Momjian 2022-08-31 22:35:09 -04:00
parent de73544bb4
commit 9072f0f618
2 changed files with 5 additions and 15 deletions

View File

@ -116,7 +116,8 @@ CREATE INDEX test1_id_index ON test1 (id);
<para>
<productname>PostgreSQL</productname> provides several index types:
B-tree, Hash, GiST, SP-GiST, GIN and BRIN.
B-tree, Hash, GiST, SP-GiST, GIN, BRIN, and the extension <link
linkend="bloom">bloom</link>.
Each index type uses a different
algorithm that is best suited to different types of queries.
By default, the <command>CREATE INDEX</command> command creates

View File

@ -143,18 +143,6 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
</listitem>
</varlistentry>
<varlistentry>
<term><literal>USING</literal></term>
<listitem>
<para>
The optional <literal>USING</literal> clause specifies an index
type as described in <xref linkend="indexes-types">. If not
specified, a default index type will be used based on the
data types of the columns.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><replaceable class="parameter">name</replaceable></term>
<listitem>
@ -183,8 +171,9 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [ IF NOT EXISTS ] <replaceable class=
<para>
The name of the index method to be used. Choices are
<literal>btree</literal>, <literal>hash</literal>,
<literal>gist</literal>, <literal>spgist</>, <literal>gin</>, and
<literal>brin</>.
<literal>gist</literal>, <literal>spgist</literal>, <literal>gin</literal>,
<literal>brin</literal>, or user-installed access methods like
<link linkend="bloom">bloom</link>.
The default method is <literal>btree</literal>.
</para>
</listitem>