diff options
| -rw-r--r-- | doc/src/sgml/ref/create_operator.sgml | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/create_operator.sgml b/doc/src/sgml/ref/create_operator.sgml index d70fefcf05c..faaf1b55b5d 100644 --- 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 --> @@ -227,6 +227,12 @@ COMMUTATOR = OPERATOR(myschema.===) , </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 specify the names of sort operators associated with a merge-joinable |