Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit52e6371

Browse files
committed
Be more clear about when to use gist__int_ops vs. gist__intbig_ops.
Per suggestion from Ron Mayer.
1 parent47ce595 commit52e6371

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

‎doc/src/sgml/intarray.sgml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/intarray.sgml,v 1.5 2007/12/10 05:32:51 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/intarray.sgml,v 1.6 2009/03/18 20:18:18 tgl Exp $ -->
22

33
<sect1 id="intarray">
44
<title>intarray</title>
@@ -237,9 +237,10 @@
237237
<para>
238238
Two GiST index operator classes are provided:
239239
<literal>gist__int_ops</> (used by default) is suitable for
240-
small and medium-sizearrays, while
240+
small- to medium-sizedata sets, while
241241
<literal>gist__intbig_ops</> uses a larger signature and is more
242-
suitable for indexing large arrays.
242+
suitable for indexing large data sets (i.e., columns containing
243+
a large number of distinct array values).
243244
</para>
244245

245246
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp