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 +, Daniel Westermann (DWE) wrote:
>
> > >
> > > I guess one "could" should be enough?
> >
> > That has been fixed, but unfortunately the copies of
Op 6/5/23 om 17:44 schreef Bruce Momjian:
On Mon, Jun 5, 2023 at 08:26:07AM +, 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; p
On 5/31/23 7:53 AM, Daniel Gustafsson wrote:
On 31 May 2023, at 13:16, Peter Eisentraut
wrote:
The first two hunks are pretty straightforward, they just move the existing
text around.
For the other two, which are not supported on Windows, I added an explicit
parenthetical note. We don't
Thanks, Bruce
From: Bruce Momjian
Sent: Monday, June 5, 2023 17:44
To: Daniel Westermann (DWE)
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: PostgreSQL 16 release notes: could cloud
On Mon, Jun 5, 2023 at 08:26:07AM +, Daniel Westermann (DWE) wrote:
>
On Mon, Jun 5, 2023 at 08:26:07AM +, 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, UP
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 perm
