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

Commit9dc12ef

Browse files
committed
Oops, missed some < and > that need to be &lt; and &gt; ...
1 parent0fb864f commit9dc12ef

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

‎doc/src/sgml/xindex.sgml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/xindex.sgml,v 1.9 2000/03/28 02:53:02 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/xindex.sgml,v 1.10 2000/03/28 02:59:55 tgl Exp $
33
Postgres documentation
44
-->
55

@@ -107,15 +107,15 @@ SELECT oid FROM pg_am WHERE amname = 'btree';
107107
impose a strict ordering on keys, lesser to greater. Since
108108
<productname>Postgres</productname> allows the user to define operators,
109109
<productname>Postgres</productname> cannot look at the name of an operator
110-
(eg, ">" or "<") and tell what kind of comparison it is. In fact,
110+
(eg, "&gt;" or "&lt;") and tell what kind of comparison it is. In fact,
111111
some access methods don't impose any ordering at all. For example,
112112
<acronym>R-tree</acronym>s express a rectangle-containment relationship,
113113
whereas a hashed data structure expresses only bitwise similarity based
114114
on the value of a hash function. <productname>Postgres</productname>
115115
needs some consistent way of taking a qualification in your query,
116116
looking at the operator and then deciding if a usable index exists. This
117117
implies that <productname>Postgres</productname> needs to know, for
118-
example, that the "<=" and ">" operators partition a
118+
example, that the "&lt;=" and "&gt;" operators partition a
119119
<acronym>B-tree</acronym>. <productname>Postgres</productname>
120120
uses strategies to express these relationships between
121121
operators and the way they can be used to scan indices.
@@ -203,7 +203,7 @@ SELECT oid FROM pg_am WHERE amname = 'btree';
203203
<note>
204204
<para>
205205
Strictly speaking, this routine can return a negative
206-
number (< 0), 0, or a non-zero positive number (> 0).
206+
number (&lt; 0), 0, or a non-zero positive number (&gt; 0).
207207
</para>
208208
</note>
209209
</para>
@@ -427,11 +427,11 @@ CREATE OPERATOR = (
427427
FROM pg_am am, pg_opclass opcl, complex_ops_tmp c
428428
WHERE amname = 'btree' AND
429429
opcname = 'complex_abs_ops' AND
430-
c.oprname = '<';
430+
c.oprname = '&lt;';
431431
</programlisting>
432432

433433
Now do this for the other operators substituting for the "1" in the
434-
third line above and the "<" in the last line. Note the order:
434+
third line above and the "&lt;" in the last line. Note the order:
435435
"less than" is 1, "less than or equal" is 2, "equal" is 3, "greater
436436
than or equal" is 4, and "greater than" is 5.
437437
</para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp