From d99e7b5a0dc15f86bc9a66de315bf5ed6f7c5271 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 6 Jan 2003 01:20:40 +0000
Subject: [PATCH] Add note explaining that a mergejoinable equality operator is
 now required if a datatype is to be accepted by GROUP BY, DISTINCT, or ORDER
 BY.  This is documentation for code changes made pursuant to pgsql-hackers
 discussion around 29-Nov-02.

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

diff --git a/doc/src/sgml/xoper.sgml b/doc/src/sgml/xoper.sgml
index 23db99705f..395306bbd6 100644
--- a/doc/src/sgml/xoper.sgml
+++ b/doc/src/sgml/xoper.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xoper.sgml,v 1.20 2002/09/21 18:32:54 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/xoper.sgml,v 1.21 2003/01/06 01:20:40 tgl Exp $
 -->
 
  <Chapter Id="xoper">
@@ -472,6 +472,17 @@ table1.column1 OP table2.column2
      </itemizedlist>
     </para>
 
+    <note>
+    <para>
+     <literal>GROUP BY</> and <literal>DISTINCT</> operations require each
+     datatype being grouped or compared to have a mergejoinable
+     equality operator named <literal>=</>.  The equality operator and its
+     associated <literal>SORT1</> operator are used to implement these
+     operations.  Also, the associated <literal>SORT1</> operator is the
+     default ordering operator for <literal>ORDER BY</>.
+    </para>
+    </note>
+
     <note>
     <para>
      In <ProductName>PostgreSQL</ProductName> versions before 7.3,