mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-31 10:07:23 +02:00
Doc: copy-editing for CREATE INDEX reference page.
Justin Pryzby, Jonathan S. Katz, and myself. Discussion: https://postgr.es/m/20181006134249.GD871@telsasoft.com
This commit is contained in:
parent
a31af2551f
commit
4d00ee4b4a
@ -612,11 +612,12 @@ Indexes:
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
Regular index builds permit other regular index builds on the
|
Regular index builds permit other regular index builds on the
|
||||||
same table to occur in parallel, but only one concurrent index build
|
same table to occur simultaneously, but only one concurrent index build
|
||||||
can occur on a table at a time. In both cases, no other types of schema
|
can occur on a table at a time. In either case, schema modification of the
|
||||||
modification on the table are allowed meanwhile. Another difference
|
table is not allowed while the index is being built. Another difference is
|
||||||
is that a regular <command>CREATE INDEX</command> command can be performed within
|
that a regular <command>CREATE INDEX</command> command can be performed
|
||||||
a transaction block, but <command>CREATE INDEX CONCURRENTLY</command> cannot.
|
within a transaction block, but <command>CREATE INDEX CONCURRENTLY</command>
|
||||||
|
cannot.
|
||||||
</para>
|
</para>
|
||||||
</refsect2>
|
</refsect2>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
@ -650,7 +651,7 @@ Indexes:
|
|||||||
ordering. For example, we might want to sort a complex-number data
|
ordering. For example, we might want to sort a complex-number data
|
||||||
type either by absolute value or by real part. We could do this by
|
type either by absolute value or by real part. We could do this by
|
||||||
defining two operator classes for the data type and then selecting
|
defining two operator classes for the data type and then selecting
|
||||||
the proper class when making an index. More information about
|
the proper class when creating an index. More information about
|
||||||
operator classes is in <xref linkend="indexes-opclass"/> and in <xref
|
operator classes is in <xref linkend="indexes-opclass"/> and in <xref
|
||||||
linkend="xindex"/>.
|
linkend="xindex"/>.
|
||||||
</para>
|
</para>
|
||||||
@ -668,12 +669,13 @@ Indexes:
|
|||||||
will be determined as if no index name had been specified in the
|
will be determined as if no index name had been specified in the
|
||||||
command.
|
command.
|
||||||
If the <literal>ONLY</literal> option is specified, no recursion
|
If the <literal>ONLY</literal> option is specified, no recursion
|
||||||
is done, and the index is marked invalid
|
is done, and the index is marked invalid.
|
||||||
(<command>ALTER INDEX ... ATTACH PARTITION</command> turns the index
|
(<command>ALTER INDEX ... ATTACH PARTITION</command> marks the index
|
||||||
valid, once all partitions acquire the index.) Note, however, that
|
valid, once all partitions acquire matching indexes.) Note, however,
|
||||||
any partition that is created in the future using
|
that any partition that is created in the future using
|
||||||
<command>CREATE TABLE ... PARTITION OF</command> will automatically
|
<command>CREATE TABLE ... PARTITION OF</command> will automatically
|
||||||
contain the index regardless of whether this option was specified.
|
have a matching index, regardless of whether <literal>ONLY</literal> is
|
||||||
|
specified.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Loading…
Reference in New Issue
Block a user