Skip to content

Commit cd55207

Browse files
committed
indices.sgml一段译文纠正
1 parent f59566c commit cd55207

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

postgresql/doc/src/sgml/indices.sgml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1716,7 +1716,7 @@ SELECT am.amname AS index_method,
17161716
</para>
17171717
-->
17181718
<para>
1719-
一个索引只能支持一个索引字段的排序。如果多个排序参与,就需要多个索引
1719+
一个索对每个索引列只能支持一种排序规则。如果需要多种排序规则,就应该建多个索引
17201720
</para>
17211721

17221722
<para>
@@ -1736,7 +1736,7 @@ CREATE INDEX test1c_content_index ON test1c (content);
17361736
The index automatically uses the collation of the
17371737
underlying column. So a query of the form
17381738
-->
1739-
索引自动使用底层字段的排序。所以一个下列格式的查询
1739+
索引自动使用底层字段的排序规则。所以一个下列格式的查询
17401740
<programlisting>
17411741
SELECT * FROM test1c WHERE content &gt; <replaceable>constant</replaceable>;
17421742
</programlisting>
@@ -1745,16 +1745,16 @@ SELECT * FROM test1c WHERE content &gt; <replaceable>constant</replaceable>;
17451745
collation of the column. However, this index cannot accelerate queries
17461746
that involve some other collation. So if queries of the form, say,
17471747
-->
1748-
可以使用这个索引,因为这个比较会默认使用这个字段的排序。然而,
1749-
这个索引不能使涉及到一些其他排序的查询加速。所以如果查询是下列格式,那么,
1748+
可以使用这个索引,因为这个比较会默认使用这一列的排序规则。然而,
1749+
这个索引不能对使用其他排序规则的查询进行加速。所以如果查询是下列格式,那么,
17501750
<programlisting>
17511751
SELECT * FROM test1c WHERE content &gt; <replaceable>constant</replaceable> COLLATE "y";
17521752
</programlisting>
17531753
<!--
17541754
are also of interest, an additional index could be created that supports
17551755
the <literal>"y"</literal> collation, like this:
17561756
-->
1757-
一个额外的索引将会建立,以支持<literal>"y"</literal>排序,像这样
1757+
可以创建一个额外的支持<literal>"y"</literal>排序规则的索引,就像这样
17581758
<programlisting>
17591759
CREATE INDEX test1c_content_y_index ON test1c (content COLLATE "y");
17601760
</programlisting>

0 commit comments

Comments
 (0)