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
Date: Mon, 5 Jun 2023 11:44:24 -0400
Message-ID: <ZH4C2L59qbtWEqSX@momjian.us> (raw)
In-Reply-To: <GV0P278MB04190997379D6B379D8CC4DFD24DA@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
References: <GV0P278MB04190997379D6B379D8CC4DFD24DA@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, daniel.westermann@dbi-services.com, pgsql-docs@lists.postgresql.org
Subject: Re: PostgreSQL 16 release notes: could cloud
In-Reply-To: <ZH4C2L59qbtWEqSX@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox