database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Be more clear about when to use gist__int_ops vs. gist__intbig_ops.

Browse Source 
Per suggestion from Ron Mayer.
This commit is contained in:
Tom Lane
2009-03-18 20:18:18 +00:00
parent 47ce595502
commit 52e6371e7d
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/intarray.sgml
View File

@ -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"> <sect1 id="intarray">
<title>intarray</title> <title>intarray</title>
@ -237,9 +237,10 @@
<para> <para>
Two GiST index operator classes are provided: Two GiST index operator classes are provided:
<literal>gist__int_ops</> (used by default) is suitable for <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 <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>
<para> <para>