|
1 | 1 | <!-- |
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 $ |
3 | 3 | Postgres documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -107,15 +107,15 @@ SELECT oid FROM pg_am WHERE amname = 'btree'; |
107 | 107 | impose a strict ordering on keys, lesser to greater. Since |
108 | 108 | <productname>Postgres</productname> allows the user to define operators, |
109 | 109 | <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, ">" or "<") and tell what kind of comparison it is. In fact, |
111 | 111 | some access methods don't impose any ordering at all. For example, |
112 | 112 | <acronym>R-tree</acronym>s express a rectangle-containment relationship, |
113 | 113 | whereas a hashed data structure expresses only bitwise similarity based |
114 | 114 | on the value of a hash function. <productname>Postgres</productname> |
115 | 115 | needs some consistent way of taking a qualification in your query, |
116 | 116 | looking at the operator and then deciding if a usable index exists. This |
117 | 117 | implies that <productname>Postgres</productname> needs to know, for |
118 | | - example, that the "<=" and ">" operators partition a |
| 118 | + example, that the "<=" and ">" operators partition a |
119 | 119 | <acronym>B-tree</acronym>. <productname>Postgres</productname> |
120 | 120 | uses strategies to express these relationships between |
121 | 121 | operators and the way they can be used to scan indices. |
@@ -203,7 +203,7 @@ SELECT oid FROM pg_am WHERE amname = 'btree'; |
203 | 203 | <note> |
204 | 204 | <para> |
205 | 205 | Strictly speaking, this routine can return a negative |
206 | | - number (< 0), 0, or a non-zero positive number (> 0). |
| 206 | + number (< 0), 0, or a non-zero positive number (> 0). |
207 | 207 | </para> |
208 | 208 | </note> |
209 | 209 | </para> |
@@ -427,11 +427,11 @@ CREATE OPERATOR = ( |
427 | 427 | FROM pg_am am, pg_opclass opcl, complex_ops_tmp c |
428 | 428 | WHERE amname = 'btree' AND |
429 | 429 | opcname = 'complex_abs_ops' AND |
430 | | - c.oprname = '<'; |
| 430 | + c.oprname = '<'; |
431 | 431 | </programlisting> |
432 | 432 |
|
433 | 433 | 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 "<" in the last line. Note the order: |
435 | 435 | "less than" is 1, "less than or equal" is 2, "equal" is 3, "greater |
436 | 436 | than or equal" is 4, and "greater than" is 5. |
437 | 437 | </para> |
|