Search Postgresql Archives

Re: "set role" semantics

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: "set role" semantics
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: Tue, 8 Nov 2022 17:24:11 -0700
Cc: pgsql-general list <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <FE0F7CE2-F1E8-40C8-A097-0CFDB0E14933@yugabyte.com>
References: <FE0F7CE2-F1E8-40C8-A097-0CFDB0E14933@yugabyte.com>

On Tue, Nov 8, 2022, 17:16 Bryn Llewellyn <bryn@xxxxxxxxxxxx> wrote:

Notice that I didn't grant "connect" on either of the databases, "d1" or "d2", to any of the roles, "clstr$mgr, "d1$mgr", or "d2$mgr".

You didn't have to since PUBLIC gets that privilege and you didn't revoke it.

https://www.postgresql.org/docs/current/ddl-priv.html

David J.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: "set role" semantics
  - From: Adrian Klaver

References:
- "set role" semantics
  - From: Bryn Llewellyn

Prev by Date: "set role" semantics
Next by Date: Re: "set role" semantics
Previous by thread: "set role" semantics
Next by thread: Re: "set role" semantics
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux