From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael.Dietrich@swisscom.com
cc: sfrost@snowman.net, pgsql-admin@lists.postgresql.org
Subject: Re: AW: Connect to db denied for superuser inherited by group
In-reply-to: <214530c2d4cb438ca204bd2a3b5b4747@swisscom.com>
References: <b93d9993e79545ffaa54d440a6f4383f@swisscom.com>
 <9cd041b2b19143758e4f4d8a752421c5@swisscom.com>
 <20180316134234.GE2416@tamriel.snowman.net>
 <214530c2d4cb438ca204bd2a3b5b4747@swisscom.com>
Comments: In-reply-to <Michael.Dietrich@swisscom.com>
	message dated "Tue, 20 Mar 2018 08:29:43 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10822.1521555101.1@sss.pgh.pa.us>
Date: Tue, 20 Mar 2018 10:11:41 -0400
Message-ID: <10823.1521555101@sss.pgh.pa.us>
Precedence: bulk

<Michael.Dietrich@swisscom.com> writes:
> What I've done
> CREATE ROLE superrole WITH  NOLOGIN  SUPERUSER ..;	
> CREATE USER nosuperuser WITH LOGIN NOSUPERUSER INHERIT ..;
> GRANT superrole TO nosuperuser WITH ADMIN OPTION;
> REVOKE CONNECT ON DATABASE nonpublicdb FROM public ;

> psql -d postgres -U nosupuser

> postgres=# set role superrole;

> postgres=# \c nonpublicdb
> FATAL:  permission denied for database " nonpublicdb "
> DETAIL:  User does not have CONNECT privilege.

> I expect that the connection to the database is allowed since a role
> with superuser is used.

You're misunderstanding what psql's \c command does.  In this form,
it attempts a connection with the new database name, but the same
username as the previous connection, ie nosupuser.  It doesn't know
anything about SET ROLE commands you may have issued to the server
while connected.

			regards, tom lane