CREATE ROLE bug?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: CREATE ROLE bug?
Date: 2023-01-25 13:29:32
Message-ID: Y9EuvCMnHxs3AqN7@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

This works in PG 15:

CREATE ROLE service CREATEROLE;
CREATE ROLE service1 WITH LOGIN IN ROLE service;
SET SESSION AUTHORIZATION service;
CREATE ROLE service2 WITH LOGIN IN ROLE service;

but generates an error in git master:

CREATE ROLE service CREATEROLE;
CREATE ROLE service1 WITH LOGIN IN ROLE service;
SET SESSION AUTHORIZATION service;
CREATE ROLE service2 WITH LOGIN IN ROLE service;
--> ERROR: must have admin option on role "service"

If I make 'service' a superuser, it works:

CREATE ROLE service SUPERUSER;
CREATE ROLE service1 WITH LOGIN IN ROLE service;
SET SESSION AUTHORIZATION service;
CREATE ROLE service2 WITH LOGIN IN ROLE service;

It is probably related to this discussion and change:

https://www.postgresql.org/message-id/flat/CA+TgmobGds7oefDjZUY+k_J7p1sS=pTq3sZ060qdb=oKei1Dkw(at)mail(dot)gmail(dot)com

I am not sure if the behavior is wrong, the error message is wrong, or
it is working as expected.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Embrace your flaws. They make you human, rather than perfect,
which you will never be.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-01-25 13:31:23 Re: plpython vs _POSIX_C_SOURCE
Previous Message Andrew 2023-01-25 13:23:11 Re: Fix to enum hashing for dump and restore