Date: Tue, 20 Jun 2023 14:05:53 +0200 (CEST)
From: Erik Wienhold <ewie@ewie.name>
To: Phani Prathyush Somayajula <phani.somayajula@pragmaticplay.com>,
	"pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Message-ID: <4796978.1031811.1687262753268@office.mailbox.org>
In-Reply-To: 
 <VI1PR10MB76716A9822F3326AF01E545C8D5CA@VI1PR10MB7671.EURPRD10.PROD.OUTLOOK.COM>
References: 
 <VI1PR10MB76716A9822F3326AF01E545C8D5CA@VI1PR10MB7671.EURPRD10.PROD.OUTLOOK.COM>
Subject: Re: Restrict Write Users
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
Archived-At: 
 <https://www.postgresql.org/message-id/4796978.1031811.1687262753268%40office.mailbox.org>
Precedence: bulk

> On 20/06/2023 13:23 CEST Phani Prathyush Somayajula <phani.somayajula@pra=
gmaticplay.com> wrote:
>
> Is there a way to restrict write access to a user by restricting the user=
 to
> have read-only on other databases on the instance. I=E2=80=99m using post=
gresql-14
> version

You should look into https://www.postgresql.org/docs/14/ddl-priv.html.

Start with a user that has no privileges and grant additional privileges as
necessary give read and/or write access.  The user must not be the owner of
database objects, must not be a member of an owner role, and must not be
a superuser.  Also check default privileges and privileges granted to PUBLI=
C.

But granting privileges in one database does not affect privileges in other
databases, except for role memberships because roles are not tied to a spec=
ific
database.

--
Erik