From: Tom Lane <tgl@sss.pgh.pa.us>
To: martin.nguyen@oracle.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18350: Modifying predefined roles' unlimited connections for
 VA STIG cybersecurity checklist
In-reply-to: <18350-ed2d82ff23d8a7e3@postgresql.org>
References: <18350-ed2d82ff23d8a7e3@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 16 Feb 2024 20:50:41 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3525668.1708119351.1@sss.pgh.pa.us>
Date: Fri, 16 Feb 2024 16:35:51 -0500
Message-ID: <3525669.1708119351@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3525669.1708119351%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> We have identified an issue where predefined roles are not modifiable,
> however a Dept. of VA security checklist requires that no roles have
> unlimited connections. The Predefined roles have unlimited connections, is
> there a way to modify these?

Solution 1: explain to your compliance department that it's pointless
to worry about the connection limit for a role that can't log in.

Solution 2: do a manual UPDATE on pg_authid.  This would have to
be done over after any major-version upgrade, though.

			regards, tom lane