From 916d8164dffedeca2318c3df70e486a63a5a01f7 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 4 Oct 2002 22:19:29 +0000
Subject: Restrict CREATE OPERATOR CLASS to superusers, per discussion some
 weeks ago.

---
 doc/src/sgml/ref/create_opclass.sgml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/ref/create_opclass.sgml b/doc/src/sgml/ref/create_opclass.sgml
index 74ac1a8d202..48f21435da5 100644
--- a/doc/src/sgml/ref/create_opclass.sgml
+++ b/doc/src/sgml/ref/create_opclass.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_opclass.sgml,v 1.3 2002/09/21 18:32:54 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_opclass.sgml,v 1.4 2002/10/04 22:19:29 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -209,9 +209,10 @@ CREATE OPERATOR CLASS
    are for different index access methods.
   </para>
   <para>
-   The user who defines an operator class becomes its owner.  The user
-   must own the data type for which the operator class is being defined,
-   and must have execute permission for all referenced operators and functions.
+   The user who defines an operator class becomes its owner.  Presently,
+   the creating user must be a superuser.  (This restriction is made because
+   an erroneous operator class definition could confuse or even crash the
+   server.)
   </para>
 
   <para>
-- 
cgit v1.2.3