Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ae73639

Browse files
committed
Mention in docs that you can create SP-GiST indexes on range types.
This is new in 9.3devel.
1 parent 4f8799a commit ae73639

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

doc/src/sgml/rangetypes.sgml

+6-6
Original file line numberDiff line numberDiff line change
@@ -371,9 +371,9 @@ SELECT '[1.234, 5.678]'::floatrange;
371371
</para>
372372

373373
<para>
374-
In addition, any range type that is meant to be used with GiST indexes
374+
In addition, any range type that is meant to be used with GiST or SP-GiST indexes
375375
should define a subtype difference, or <literal>subtype_diff</>, function.
376-
(A GiST index will still work without <literal>subtype_diff</>, but it is
376+
(the index will still work without <literal>subtype_diff</>, but it is
377377
likely to be considerably less efficient than if a difference function is
378378
provided.) The subtype difference function takes two input values of the
379379
subtype, and returns their difference (i.e., <replaceable>X</> minus
@@ -394,7 +394,7 @@ SELECT '[1.234, 5.678]'::floatrange;
394394
</para>
395395
</sect2>
396396

397-
<sect2 id="rangetypes-gist">
397+
<sect2 id="rangetypes-indexing">
398398
<title>Indexing</title>
399399

400400
<indexterm>
@@ -403,12 +403,12 @@ SELECT '[1.234, 5.678]'::floatrange;
403403
</indexterm>
404404

405405
<para>
406-
GiST indexes can be created for table columns of range types.
407-
For instance:
406+
GiST and SP-GiST indexes can be created for table columns of range types.
407+
For instance, to create a GiST index:
408408
<programlisting>
409409
CREATE INDEX reservation_idx ON reservation USING gist (during);
410410
</programlisting>
411-
A GiST index can accelerate queries involving these range operators:
411+
A GiST or SP-GiST index can accelerate queries involving these range operators:
412412
<literal>=</>,
413413
<literal>&amp;&amp;</>,
414414
<literal>&lt;@</>,

0 commit comments

Comments
 (0)