Re: Restricting user to see schema structure - Mailing list pgsql-general

From David G. Johnston
Subject Re: Restricting user to see schema structure
Date
Msg-id CAKFQuwZrgdPeoneH8j1oHOBDpbWJwz_iB=HeBGXU6M1rcOgnPQ@mail.gmail.com
Whole thread Raw
In response to Re: Restricting user to see schema structure  (Bryn Llewellyn <bryn@yugabyte.com>)
Responses Re: Restricting user to see schema structure
List pgsql-general
On Mon, May 16, 2022 at 10:21 PM Bryn Llewellyn <bryn@yugabyte.com> wrote:

Right, I see the importance of this now. I now realize that when a database is created, CONNECT on it is automatically granted to PUBLIC. But there's no mention of this (or what to read to learn that this is the case) in the "pg_hba.conf" chapter. Nor does the section on the CREATE DATABASE statement mention this. How is the neophyte supposed to know about this behavior?

By reading the documentation, specifically the chapter linked before, where this is discussed.


Not saying there isn't room for improvement here, I tend to agree that the SQL Command Reference section should be considered a primary jumping off point.  But the chapter on Data Definition is basically mandatory reading once a DBA wants to do any non-trivial modifications to their cluster.

David J.

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Alternative to slow SRF in SELECT?
Next
From: Dan Lynch
Date:
Subject: Postgres AST Deparser for Postgres