projects
/
users
/
simon
/
postgres.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
8ff044c
)
Be more clear about when to use gist__int_ops vs. gist__intbig_ops.
author
Tom Lane
<tgl@sss.pgh.pa.us>
Wed, 18 Mar 2009 20:18:18 +0000
(20:18 +0000)
committer
Tom Lane
<tgl@sss.pgh.pa.us>
Wed, 18 Mar 2009 20:18:18 +0000
(20:18 +0000)
Per suggestion from Ron Mayer.
doc/src/sgml/intarray.sgml
patch
|
blob
|
blame
|
history
diff --git
a/doc/src/sgml/intarray.sgml
b/doc/src/sgml/intarray.sgml
index 9238a5c9c296b4b4a95523f26dcefe5b4c7a40b3..f482432f87b1fdca89b5e1613457ed7fc9b79ae9 100644
(file)
--- 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 array
s, while
+ small
- to medium-size data set
s, 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>