From: Tom Lane Date: Mon, 6 Jan 2003 01:20:40 +0000 (+0000) Subject: Add note explaining that a mergejoinable equality operator is now X-Git-Tag: REL7_4_BETA1~1293 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d99e7b5a0dc15f86bc9a66de315bf5ed6f7c5271;p=thirdparty%2Fpostgresql.git 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. --- diff --git a/doc/src/sgml/xoper.sgml b/doc/src/sgml/xoper.sgml index 23db99705f7..395306bbd60 100644 --- a/doc/src/sgml/xoper.sgml +++ b/doc/src/sgml/xoper.sgml @@ -1,5 +1,5 @@ @@ -472,6 +472,17 @@ table1.column1 OP table2.column2 + + + GROUP BY and DISTINCT operations require each + datatype being grouped or compared to have a mergejoinable + equality operator named =. The equality operator and its + associated SORT1 operator are used to implement these + operations. Also, the associated SORT1 operator is the + default ordering operator for ORDER BY. + + + In PostgreSQL versions before 7.3,