mirror of
https://github.com/postgres/postgres.git
synced 2025-07-12 21:01:52 +03:00
docs: consistently uppercase index method and add spacing
Consistently uppercase index method names, e.g. GIN, and add space after the index method name and the parentheses enclosing the column names.
This commit is contained in:
@ -375,13 +375,13 @@ SELECT '"foo"'::jsonb ? 'foo';
|
||||
implement, see <xref linkend="functions-jsonb-op-table">.)
|
||||
An example of creating an index with this operator class is:
|
||||
<programlisting>
|
||||
CREATE INDEX idxgin ON api USING gin (jdoc);
|
||||
CREATE INDEX idxgin ON api USING GIN (jdoc);
|
||||
</programlisting>
|
||||
The non-default GIN operator class <literal>jsonb_path_ops</>
|
||||
supports indexing the <literal>@></> operator only.
|
||||
An example of creating an index with this operator class is:
|
||||
<programlisting>
|
||||
CREATE INDEX idxginp ON api USING gin (jdoc jsonb_path_ops);
|
||||
CREATE INDEX idxginp ON api USING GIN (jdoc jsonb_path_ops);
|
||||
</programlisting>
|
||||
</para>
|
||||
|
||||
@ -426,7 +426,7 @@ SELECT jdoc->'guid', jdoc->'name' FROM api WHERE jdoc -> 'tags' ? 'qui'
|
||||
the <literal>"tags"</> key is common, defining an index like this
|
||||
may be worthwhile:
|
||||
<programlisting>
|
||||
CREATE INDEX idxgintags ON api USING gin ((jdoc -> 'tags'));
|
||||
CREATE INDEX idxgintags ON api USING GIN ((jdoc -> 'tags'));
|
||||
</programlisting>
|
||||
Now, the <literal>WHERE</> clause <literal>jdoc -> 'tags' ? 'qui'</>
|
||||
will be recognized as an application of the indexable
|
||||
|
Reference in New Issue
Block a user