Add a cross-reference to precedence information to CREATE OPERATOR's

documentation.  Per suggestion from Marc Cousin.

diff --git a/doc/src/sgml/ref/create_operator.sgml b/doc/src/sgml/ref/create_operator.sgml
index d70fefcf05c93a15570944d29cb09b9912502a59..faaf1b55b5d7cd7043bba7e8401e8eb5c4d280b0 100644 (file)
--- a/doc/src/sgml/ref/create_operator.sgml
+++ b/doc/src/sgml/ref/create_operator.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.53 2010/06/22 11:36:16 rhaas Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.54 2010/07/08 16:30:13 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -226,6 +226,12 @@ COMMUTATOR = OPERATOR(myschema.===) ,
    Refer to <xref linkend="xoper"> for further information.
   </para>
 
+  <para>
+   It is not possible to specify an operator's lexical precedence in
+   <command>CREATE OPERATOR</>, because the parser's precedence behavior
+   is hard-wired.  See <xref linkend="sql-precedence"> for precedence details.
+  </para>
+
   <para>
    The obsolete options <literal>SORT1</>, <literal>SORT2</>,
    <literal>LTCMP</>, and <literal>GTCMP</> were formerly used to