From 99ef5152801789dfe04b76a4feb675e4191b72e5 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Wed, 24 Feb 2010 15:54:31 +0000
Subject: Revert removal of pre-7.4 documenation behavior mentions.

---
 doc/src/sgml/xindex.sgml | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

(limited to 'doc/src/sgml/xindex.sgml')

diff --git a/doc/src/sgml/xindex.sgml b/doc/src/sgml/xindex.sgml
index fa9fecf5ba3..1da74b9fa3d 100644
--- a/doc/src/sgml/xindex.sgml
+++ b/doc/src/sgml/xindex.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/xindex.sgml,v 1.65 2010/02/24 03:33:49 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/xindex.sgml,v 1.66 2010/02/24 15:54:31 momjian Exp $ -->
 
 <sect1 id="xindex">
  <title>Interfacing Extensions To Indexes</title>
@@ -895,6 +895,16 @@ ALTER OPERATOR FAMILY integer_ops USING btree ADD
    try to use these SQL features with the data type.
   </para>
 
+   <note>
+    <para>
+     In <productname>PostgreSQL</productname> versions before 7.4,
+     sorting and grouping operations would implicitly use operators named
+     <literal>=</>, <literal>&lt;</>, and <literal>&gt;</>.  The new
+     behavior of relying on default operator classes avoids having to make
+     any assumption about the behavior of operators with particular names.
+    </para>
+   </note>
+
   <para>
    Another important point is that an operator that
    appears in a hash operator family is a candidate for hash joins,
-- 
cgit v1.2.3