Re: Basic Questions about PostgreSQL.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: A Z <poweruserm(at)live(dot)com(dot)au>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Basic Questions about PostgreSQL.
Date: 2021-09-15 05:32:13
Message-ID: CAKFQuwbVifHzCdcFDLN3NBY7W+T+nC54DKXK6voODd3uX+9Fyw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wednesday, September 15, 2021, A Z <poweruserm(at)live(dot)com(dot)au> wrote:

> -In PostgreSQL, what is the difference between Roles, Groups
>
>
There is none, aside from convention. Roles are generic, groups don’t get
login rights while users do.

You might want to clarify what you mean by policy since referencing the
“create policy” command seems out of place here.

> -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?
>
>
Manipulating the pg_hba.comf file is usually the most efficient method.

Though since connect privileges are usually left as strictly inherited from
public by default revoking connect from public will most likely prevent
non-superusers from connecting to databases.

Though it seems unusual that maintenance would require such extreme
measures to be taken.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Brent Wood 2021-09-15 06:04:18 Re: SQL queries as sets: was The tragedy of SQL
Previous Message Guyren Howe 2021-09-15 05:31:41 Re: SQL queries as sets: was The tragedy of SQL