| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | kolpasch(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18717: ALTER ROLE SET ROLE functionality is broken |
| Date: | 2024-11-20 15:48:27 |
| Message-ID: | Zz4Ey8mMhbyl8oJq@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 20, 2024 at 12:33:41PM +0000, PG Bug reporting form wrote:
> We grant the owner role to the login roles, and assign it by ALTER ROLE
> <login_role> SET ROLE = <owner_role>. As a result, when logging into the
> database with a login role, it is automatically assigned the owner role.
>
> Starting with version 14.14, this behavior is broken, and the issue persists
> in version 17.1. When connecting to the database with a login role, the
> session is assigned an empty (none) value for the role, leaving users
> without the necessary permissions.
This should be fixed in the next set of minor versions scheduled for
release tomorrow [0].
[0] https://postgr.es/c/7b88529
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-11-20 15:54:50 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |
| Previous Message | Tom Lane | 2024-11-20 15:39:35 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |