From: Robert Haas <rhaas@postgresql.org>
Date: Fri, 3 Dec 2010 14:29:14 +0000 (-0500)
Subject: Clarify that LOCK TABLE requires a table-level privilege.
X-Git-Tag: REL9_1_ALPHA3~96
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c0a4d3e0511b4d1f7996451329deaa2acd0e18fa;p=thirdparty%2Fpostgresql.git

Clarify that LOCK TABLE requires a table-level privilege.
---

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>