Re: PostgreSQL 16 release notes: could cloud

From: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL 16 release notes: could cloud
Date: 2023-06-05 15:54:31
Message-ID: GV0P278MB0419EC52E97C8F1AF096B933D24DA@GV0P278MB0419.CHEP278.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Thanks, Bruce

________________________________
From: Bruce Momjian <bruce(at)momjian(dot)us>
Sent: Monday, June 5, 2023 17:44
To: Daniel Westermann (DWE) <daniel(dot)westermann(at)dbi-services(dot)com>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL 16 release notes: could cloud

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(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Jonathan S. Katz 2023-06-05 17:10:01 Re: confusing positioning of notes in connection settings
Previous Message Bruce Momjian 2023-06-05 15:44:24 Re: PostgreSQL 16 release notes: could cloud