non-superusers are allowed to drop the replication user, but are not allowed to alter or even create them, is that ok? - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject non-superusers are allowed to drop the replication user, but are not allowed to alter or even create them, is that ok?
Date
Msg-id CAE9k0PmWZQTPMUxF3-mPcPjKaU+QZ-ydTZ+PRhdbaB2gNjJPhQ@mail.gmail.com
Whole thread Raw
Responses Re: non-superusers are allowed to drop the replication user, but are not allowed to alter or even create them, is that ok?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Re: non-superusers are allowed to drop the replication user, but are not allowed to alter or even create them, is that ok?  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
Hi All,

While working on one of the internal projects I noticed that currently in Postgres, we do not allow normal users to alter attributes of the replication user. However we do allow normal users to drop replication users or to even rename it using the alter command. Is that behaviour ok? If yes, can someone please help me understand how and why this is okay.

Here is an example illustrating this behaviour:

supusr@postgres=# create user repusr with password 'repusr' replication;
CREATE ROLE

supusr@postgres=# create user nonsu with password 'nonsu' createrole createdb;
CREATE ROLE

supusr@postgres=# \c postgres nonsu;
You are now connected to database "postgres" as user "nonsu".

nonsu@postgres=> alter user repusr nocreatedb;
ERROR:  42501: must be superuser to alter replication roles or change replication attribute

nonsu@postgres=> alter user repusr rename to refusr;
ALTER ROLE

nonsu@postgres=> drop user refusr;
DROP ROLE

nonsu@postgres=> create user repusr2 with password 'repusr2' replication;
ERROR:  42501: must be superuser to create replication users

--
With Regards,
Ashutosh Sharma.

pgsql-hackers by date:

Previous
From: Jelte Fennema
Date:
Subject: Add ETIMEDOUT to ALL_CONNECTION_FAILURE_ERRNOS
Next
From: Amit Kapila
Date:
Subject: Re: pgsql: Document XLOG_INCLUDE_XID a little better