summaryrefslogtreecommitdiff
path: root/doc/src/sgml/btree-gin.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/btree-gin.sgml')
-rw-r--r--doc/src/sgml/btree-gin.sgml12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/sgml/btree-gin.sgml b/doc/src/sgml/btree-gin.sgml
index d2142028eb5..8c3cb026960 100644
--- a/doc/src/sgml/btree-gin.sgml
+++ b/doc/src/sgml/btree-gin.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/btree-gin.sgml,v 1.1 2009/03/25 23:20:01 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/btree-gin.sgml,v 1.2 2010/08/17 04:37:20 petere Exp $ -->
<sect1 id="btree-gin">
<title>btree_gin</title>
@@ -9,7 +9,7 @@
<para>
<filename>btree_gin</> provides sample GIN operator classes that
- implement B-Tree equivalent behavior for the data types
+ implement B-tree equivalent behavior for the data types
<type>int2</>, <type>int4</>, <type>int8</>, <type>float4</>,
<type>float8</>, <type>timestamp with time zone</>,
<type>timestamp without time zone</>, <type>time with time zone</>,
@@ -21,12 +21,12 @@
<para>
In general, these operator classes will not outperform the equivalent
- standard btree index methods, and they lack one major feature of the
- standard btree code: the ability to enforce uniqueness. However,
+ standard B-tree index methods, and they lack one major feature of the
+ standard B-tree code: the ability to enforce uniqueness. However,
they are useful for GIN testing and as a base for developing other
GIN operator classes. Also, for queries that test both a GIN-indexable
- column and a btree-indexable column, it might be more efficient to create
- a multi-column GIN index that uses one of these opclasses than to create
+ column and a B-tree-indexable column, it might be more efficient to create
+ a multicolumn GIN index that uses one of these operator classes than to create
two separate indexes that would have to be combined via bitmap ANDing.
</para>