summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2009-03-18 20:18:18 +0000
committerTom Lane2009-03-18 20:18:18 +0000
commitedd0b0a091bfab0f13e6d6d9d9d1fe8adb79ce81 (patch)
tree41723aacc6f37556dace57245ec64e2276dea49a
parent8ff044cdbc11fcee6fde6a236c5efaca7ccd9296 (diff)
Be more clear about when to use gist__int_ops vs. gist__intbig_ops.
Per suggestion from Ron Mayer.
-rw-r--r--doc/src/sgml/intarray.sgml5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/intarray.sgml b/doc/src/sgml/intarray.sgml
index 9238a5c9c2..f482432f87 100644
--- a/doc/src/sgml/intarray.sgml
+++ b/doc/src/sgml/intarray.sgml
@@ -237,9 +237,10 @@
<para>
Two GiST index operator classes are provided:
<literal>gist__int_ops</> (used by default) is suitable for
- small and medium-size arrays, while
+ small- to medium-size data sets, while
<literal>gist__intbig_ops</> uses a larger signature and is more
- suitable for indexing large arrays.
+ suitable for indexing large data sets (i.e., columns containing
+ a large number of distinct array values).
</para>
<para>