Обсуждение: PostgreSQL 16 release notes: could cloud
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 canissue all lock levels. MORE? I guess one "could" should be enough? Regards Daniel
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 canissue 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.
Thanks, Bruce
From: Bruce Momjian <bruce@momjian.us>
Sent: Monday, June 5, 2023 17:44
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
Sent: Monday, June 5, 2023 17:44
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
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.
> 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.
Op 6/5/23 om 17:44 schreef Bruce Momjian: > On Mon, Jun 5, 2023 at 08:26:07AM +0000, Daniel Westermann (DWE) wrote: >> >> 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 'PRAPARE/EXECUTE' should be 'PREPARE/EXECUTE' Erik
On Mon, Jun 5, 2023 at 07:12:35PM +0200, Erik Rijkers wrote: > Op 6/5/23 om 17:44 schreef Bruce Momjian: > > On Mon, Jun 5, 2023 at 08:26:07AM +0000, Daniel Westermann (DWE) wrote: > > > > > > > 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 > > 'PRAPARE/EXECUTE' should be > 'PREPARE/EXECUTE' Thanks, fixed. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.