Date: Mon, 5 Jun 2023 11:44:24 -0400
From: Bruce Momjian <bruce@momjian.us>
To: "Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>
Cc: "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Subject: Re: PostgreSQL 16 release notes: could cloud
Message-ID: <ZH4C2L59qbtWEqSX@momjian.us>
References: 
 <GV0P278MB04190997379D6B379D8CC4DFD24DA@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <GV0P278MB04190997379D6B379D8CC4DFD24DA@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
Archived-At: 
 <https://www.postgresql.org/message-id/ZH4C2L59qbtWEqSX%40momjian.us>
Precedence: bulk

On Mon, Jun  5, 2023 at 08:26:07AM +0000, Daniel Westermann (DWE) wrote:
> Hi,
> 
> E.1.3.1.4. Privileges #
> 
> Simplify permissions for LOCK TABLE (Jeff Davis)
> 
> Previously the ability to perform LOCK TABLE at various lock levels was bound to specific query-type permissions. For example, UPDATE could could perform all lock levels except ACCESS SHARE, which required SELECT permissions. Now UPDATE can issue all lock levels. MORE?
> 
> I guess one "could" should be enough?

That has been fixed, but unfortunately the copies of the release notes
on the community website are unchanged since beta1 was packaged;  please
see the current contents here:

	https://momjian.us/pgsql_docs/release-16.html

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.