Basic Questions about PostgreSQL.

From: A Z <poweruserm(at)live(dot)com(dot)au>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Basic Questions about PostgreSQL.
Date: 2021-09-15 05:10:40
Message-ID: PSXP216MB0085C55229D76B403FBE3E6A9ADB9@PSXP216MB0085.KORP216.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-In PostgreSQL, what is the difference between Roles, Groups, and Policies exactly? What are they each, how do they relate to one another, and which one(s) can be assigned to another?

-Is there a simple, immediate, straightforward way to temporarily disable PostgreSQL database
use of all other users, except development users, or in fact just one user (one developer, yourself)
so that maintenance on the data or the data model may be performed?

The way things are, after you revoke connection priviledges for all the other general users,
cancel all the other connections (except for yourself, or developer user access),
and then perform required maintenance on the database. Thereafter, connection priviledges
have to be restored to all the other users, so that they can choose to connect again.

All of this strikes me as being very elaborate. Is there a much more simple
way to disable all and subsequent connections to a database, temporarily, and
then allowing them all again, within the PostgreSQL DBMS?

Is there a public Extension, for example, that installs and works well, which can be used to do this?
Is there a simple, one hit way to turn a set of user connections all off, and then all on
(regarding their permissions and connections, I presume), again?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Guyren Howe 2021-09-15 05:31:41 Re: SQL queries as sets: was The tragedy of SQL
Previous Message Steve Litt 2021-09-15 04:54:49 SQL queries as sets: was The tragedy of SQL