Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: harukat(at)sraoss(dot)co(dot)jp, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."
Date: 2023-09-29 18:32:33
Message-ID: ZRcYQRLZFRa5+Gxa@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Sep 29, 2023 at 02:17:20PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Thu, Sep 28, 2023 at 07:24:35AM +0000, PG Bug reporting form wrote:
> >> In the following release note item, it seems that "GRANT group_name TO
> >> user_name"
> >> should be "ALTER GROUP group_name ADD USER user_name".
> >> As far as I have tested and confirmed, ALTER GROUP is the one that
> >> has been allowed since version 16.
>
> > Yes, you are correct. Attached patch applied.
>
> Should probably change the <link> target too?

Ah, good point, done.

--
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-bugs by date

  From Date Subject
Next Message Jov 2023-09-30 06:36:18 Re: BUG #18134: ROW_COUNT do not set to 0 when psql's \gset command get no rows returned
Previous Message Tom Lane 2023-09-29 18:17:20 Re: BUG #18137: PG16 release note doc bug in "Allow GRANT group_name TO user_name ..."