From 52e6371e7d7034e9142d8de204a3c3d045c12d13 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 18 Mar 2009 20:18:18 +0000
Subject: [PATCH] Be more clear about when to use gist__int_ops vs.
 gist__intbig_ops. Per suggestion from Ron Mayer.

---
 doc/src/sgml/intarray.sgml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/intarray.sgml b/doc/src/sgml/intarray.sgml
index 95121c1e9b..ddf7421899 100644
--- a/doc/src/sgml/intarray.sgml
+++ b/doc/src/sgml/intarray.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/intarray.sgml,v 1.5 2007/12/10 05:32:51 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/intarray.sgml,v 1.6 2009/03/18 20:18:18 tgl Exp $ -->
 
 <sect1 id="intarray">
  <title>intarray</title>
@@ -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>
-- 
2.40.0