From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 18 Mar 2009 20:18:18 +0000 (+0000)
Subject: Be more clear about when to use gist__int_ops vs. gist__intbig_ops.
X-Git-Url: http://waps.l3s.uni-hannover.de/gitweb/?a=commitdiff_plain;h=edd0b0a091bfab0f13e6d6d9d9d1fe8adb79ce81;p=users%2Fsimon%2Fpostgres.git

Be more clear about when to use gist__int_ops vs. gist__intbig_ops.
Per suggestion from Ron Mayer.
---

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>