Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commita6677f0

Browse files
committed
Change "indices" to "indexes", per OED.
1 parentf000ffd commita6677f0

20 files changed

+121
-126
lines changed

‎doc/src/sgml/arch-dev.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.13 2000/12/26 00:10:37 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.14 2001/05/17 21:50:15 petere Exp $
33
-->
44

55
<chapter id="overview">
@@ -603,7 +603,7 @@ current context are performed.
603603

604604
<para>
605605
The planner/optimizer decides which plans should be generated
606-
based upon the types ofindices defined on the relations appearing in
606+
based upon the types ofindexes defined on the relations appearing in
607607
a query. There is always the possibility of performing a
608608
sequential scan on a relation, so a plan using only
609609
sequential scans is always created. Assume an index is defined on a
@@ -612,7 +612,7 @@ current context are performed.
612612
<literal>relation.attribute OPR constant</literal>. If
613613
<literal>relation.attribute</literal> happens to match the key of the B-tree
614614
index and <literal>OPR</literal> is anything but '&lt;&gt;' another plan is created using
615-
the B-tree index to scan the relation. If there are furtherindices
615+
the B-tree index to scan the relation. If there are furtherindexes
616616
present and the restrictions in the query happen to match a key of an
617617
index further plans will be considered.
618618
</para>
@@ -889,7 +889,7 @@ The {\tt AGG} node is followed by a {\tt GRP} node. The implementation
889889
of the {\it grouping} logic needs a sorted table for its operation so
890890
the {\tt GRP} node is followed by a {\tt SORT} node. The {\tt SORT}
891891
operation gets its tuples from a kind of {\tt Scan} node (if no
892-
indices are present this will be a simple {\tt SeqScan} node). Any
892+
indexes are present this will be a simple {\tt SeqScan} node). Any
893893
qualifications present are attached to the {\tt Scan} node. Figure
894894
\ref{plan_having} shows the {\it plan} created for the query given in
895895
example \ref{having}.

‎doc/src/sgml/backup.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.8 2001/05/17 21:12:48 petere Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.9 2001/05/17 21:50:15 petere Exp $ -->
22
<chapter id="backup">
33
<title>Backup and Restore</title>
44

@@ -355,7 +355,7 @@ tar -cf backup.tar /usr/local/pgsql/data
355355
Also note that the file system backup will not necessarily be
356356
smaller than an SQL dump. On the contrary, it will most likely be
357357
larger. (<application>pg_dump</application> does not need to dump
358-
the contents ofindices for example, just the commands to recreate
358+
the contents ofindexes for example, just the commands to recreate
359359
them.)
360360
</para>
361361

‎doc/src/sgml/extend.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.9 2001/01/13 23:58:55 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.10 2001/05/17 21:50:15 petere Exp $
33
-->
44

55
<chapter id="extend">
@@ -96,7 +96,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.9 2001/01/13 23:58:55 peter
9696
file that stores all rows of a table) but the
9797
user can "look inside" at the attributes of these types
9898
from the query language and optimize their retrieval by
99-
(for example) definingindices on the attributes.
99+
(for example) definingindexes on the attributes.
100100
<productname>Postgres</productname> base types are further
101101
divided into built-in
102102
types and user-defined types. Built-in types (like
@@ -149,7 +149,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.9 2001/01/13 23:58:55 peter
149149
</row>
150150
<row>
151151
<entry>pg_index</entry>
152-
<entry> secondaryindices</entry>
152+
<entry> secondaryindexes</entry>
153153
</row>
154154
<row>
155155
<entry>pg_proc</entry>
@@ -256,7 +256,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.9 2001/01/13 23:58:55 peter
256256
pg_am, pg_amop, pg_amproc, pg_operator and
257257
pg_opclass are particularly hard to understand
258258
and will be described in depth (in the section
259-
on interfacing types and operators toindices)
259+
on interfacing types and operators toindexes)
260260
after we have discussed basic extensions.
261261
</para>
262262
</listitem>

‎doc/src/sgml/geqo.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/geqo.sgml,v 1.16 2001/04/20 15:52:33 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/geqo.sgml,v 1.17 2001/05/17 21:50:15 petere Exp $
33
Genetic Optimizer
44
-->
55

@@ -51,8 +51,8 @@ Genetic Optimizer
5151
<firstterm>join methods</firstterm>
5252
(e.g., nested loop, hash join, merge join in <productname>Postgres</productname>) to
5353
process individual <command>join</command>s and a diversity of
54-
<firstterm>indices</firstterm> (e.g.,r-tree,
55-
b-tree, hash in <productname>Postgres</productname>) as access paths for relations.
54+
<firstterm>indexes</firstterm> (e.g.,R-tree,
55+
B-tree, hash in <productname>Postgres</productname>) as access paths for relations.
5656
</para>
5757

5858
<para>

‎doc/src/sgml/gist.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
</AuthorGroup>
99
<Date>Transcribed 1998-02-19</Date>
1010
</DocInfo>
11-
<Title>GiSTIndices</Title>
11+
<Title>GiSTIndexes</Title>
1212

1313
<Para>
1414
The information about GIST is at

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp