diff options
| author | Bruce Momjian <bruce@momjian.us> | 2023-08-31 15:14:18 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2023-08-31 15:14:18 -0400 |
| commit | 22297cd65fa5efeffebcfaebfdda174dcdbd821a (patch) | |
| tree | 17c67b1258225c21884c32d49acdada193607f02 | |
| parent | d5feb6011e629cc1096bbaa10af5ffcc6c17f908 (diff) | |
| download | postgresql-22297cd65fa5efeffebcfaebfdda174dcdbd821a.tar.gz postgresql-22297cd65fa5efeffebcfaebfdda174dcdbd821a.zip | |
doc: PG 16 relnotes: clarify LOCK TABLE description
Backpatch-through: 16 only
| -rw-r--r-- | doc/src/sgml/release-16.sgml | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/src/sgml/release-16.sgml b/doc/src/sgml/release-16.sgml index 2eb172eaa63..9816012631c 100644 --- a/doc/src/sgml/release-16.sgml +++ b/doc/src/sgml/release-16.sgml @@ -948,14 +948,15 @@ Author: Jeff Davis <jdavis@postgresql.org> </para> <para> - Previously the ability to perform <command>LOCK - TABLE</command> at various lock levels was bound to - specific query-type permissions. For example, <link + Previously a user's ability to perform <command>LOCK + TABLE</command> at various lock levels was limited to the + 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> - could perform all lock levels except - <literal>ACCESS SHARE</literal>, which required <link - linkend="sql-select"><command>SELECT</command></link> permissions. - Now <command>UPDATE</command> can issue all lock levels. MORE? + permission could perform all lock levels except <literal>ACCESS + SHARE</literal>, even though it was a lesser lock level. Now users + can issue lesser lock levels if they already have permission for + greater lock levels. </para> </listitem> |