Remove example of SQL-standard syntax for GRANT/REVOKE --- was causing

confusion.

diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml
index 080df2b044a6fa35943731a6ea6859a9d673981b..a4c3b0d44085eb9ea31d187cb3642dcf8baae858 100644 (file)
--- a/doc/src/sgml/ref/grant.sgml
+++ b/doc/src/sgml/ref/grant.sgml
@@ -1,5 +1,5 @@
 
 
@@ -520,14 +520,8 @@ GRANT admins TO joe;
    
 
    
-    The SQL standard allows setting privileges for individual columns
-    within a table:
-
-
-GRANT privileges
-    ON table [ ( column [, ...] ) ] [, ...]
-    TO { PUBLIC | username [, ...] } [ WITH GRANT OPTION ]
-
+    PostgreSQL does not support the SQL-standard 
+    functionality of setting privileges for individual columns.
    
 
    

diff --git a/doc/src/sgml/ref/revoke.sgml b/doc/src/sgml/ref/revoke.sgml
index caf62b78331fe994dd7d02cf6e473806d3cec836..412da611e2d530d3d36e8f5882a17142af80c49a 100644 (file)
--- a/doc/src/sgml/ref/revoke.sgml
+++ b/doc/src/sgml/ref/revoke.sgml
@@ -1,5 +1,5 @@
 
 
@@ -231,15 +231,8 @@ REVOKE admins FROM joe;
 
    
     The compatibility notes of the  command
-    apply analogously to REVOKE.  The syntax summary is:
-
-
-REVOKE [ GRANT OPTION FOR ] privileges
-    ON object [ ( column [, ...] ) ]
-    FROM { PUBLIC | username [, ...] }
-    { RESTRICT | CASCADE }
-
-    One of RESTRICT or CASCADE
+    apply analogously to REVOKE.
+    RESTRICT or CASCADE
     is required according to the standard, but PostgreSQL
     assumes RESTRICT by default.