Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit22297cd

Browse files
committed
doc: PG 16 relnotes: clarify LOCK TABLE description
Backpatch-through: 16 only
1 parentd5feb60 commit22297cd

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

‎doc/src/sgml/release-16.sgml

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -948,14 +948,15 @@ Author: Jeff Davis <jdavis@postgresql.org>
948948
</para>
949949

950950
<para>
951-
Previously the ability to perform <command>LOCK
952-
TABLE</command> at various lock levels was bound to
953-
specific query-type permissions. For example, <link
951+
Previously a user's ability to perform <command>LOCK
952+
TABLE</command> at various lock levels was limited to the
953+
lock levels required by the commands they had permission
954+
to execute on the table. For example, someone with <link
954955
linkend="sql-update"><command>UPDATE</command></link>
955-
could perform all lock levels except
956-
<literal>ACCESSSHARE</literal>,which required <link
957-
linkend="sql-select"><command>SELECT</command></link> permissions.
958-
Now <command>UPDATE</command> can issue alllock levels. MORE?
956+
permissioncould perform all lock levels except <literal>ACCESS
957+
SHARE</literal>,even though it was a lesser lock level. Now users
958+
can issue lesser lock levels if they already have permission for
959+
greaterlock levels.
959960
</para>
960961
</listitem>
961962

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp