postgres.git / summary / log / commit / refs

commit    c0a4d3e0511b4d1f7996451329deaa2acd0e18fa
Author:   Robert Haas <rhaas@postgresql.org>
Date:     Fri Dec 03 14:29:14 2010 +0000
First released in: 9.1.0

    Clarify that LOCK TABLE requires a table-level privilege.


 doc/src/sgml/ref/lock.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml
index 0c960aa622b..86cd744ea4b 100644
--- a/doc/src/sgml/ref/lock.sgml
+++ b/doc/src/sgml/ref/lock.sgml
@@ -158,7 +158,7 @@ LOCK [ TABLE ] [ ONLY ] <replaceable class="PARAMETER">name</replaceable> [, ...
    <para>
     <literal>LOCK TABLE ... IN ACCESS SHARE MODE</> requires <literal>SELECT</>
     privileges on the target table.  All other forms of <command>LOCK</>
-    require at least one of <literal>UPDATE</>, <literal>DELETE</>, or
+    require table-level <literal>UPDATE</>, <literal>DELETE</>, or
     <literal>TRUNCATE</> privileges.
    </para>
 


[parent: 5ef6c913836b]