database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00
Code

doc: PG 16 relnotes: clarify LOCK TABLE description

Browse Source 
Backpatch-through: 16 only
This commit is contained in:
Bruce Momjian 2023-08-31 15:14:18 -04:00
parent d5feb6011e
commit 22297cd65f
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/sgml/release-16.sgml
View File

@ -948,14 +948,15 @@ Author: Jeff Davis <jdavis@postgresql.org>
</para> </para>
<para> <para>
Previously the ability to perform <command>LOCK Previously a user's ability to perform <command>LOCK
TABLE</command> at various lock levels was bound to TABLE</command> at various lock levels was limited to the
specific query-type permissions. For example, <link lock levels required by the commands they had permission
to execute on the table. For example, someone with <link
linkend="sql-update"><command>UPDATE</command></link> linkend="sql-update"><command>UPDATE</command></link>
could perform all lock levels except permission could perform all lock levels except <literal>ACCESS
<literal>ACCESS SHARE</literal>, which required <link SHARE</literal>, even though it was a lesser lock level. Now users
linkend="sql-select"><command>SELECT</command></link> permissions. can issue lesser lock levels if they already have permission for
Now <command>UPDATE</command> can issue all lock levels. MORE? greater lock levels.
</para> </para>
</listitem> </listitem>