Postgres Pro
Downloads
Home   >   mailing lists

Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC
Date
Msg-id CAKAnmm+qs8yrviNEbdJf-NLwBiYSxWYN0RHJkcCTjZZVyY8huA@mail.gmail.com
Whole thread Raw
In response to Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC
List pgsql-general
Tree view
On Thu, Sep 12, 2024 at 9:12 AM Dominique Devienne <ddevienne@gmail.com> wrote:
On Thu, Sep 12, 2024 at 3:06 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
> (Also note that determining if a database or user exists does not even require a successful login to the cluster.)

Hi. How so? I was not aware of such possibilities.
Can you please give pointers (docs, examples) of this?

$ psql -U eve
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  role "eve" does not exist

$ psql -U postgres -d theater
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  database "theater" does not exist 

$ psql -U alice -d template1
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for user "alice"

Cheers,
Greg

pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: Backward compat issue with v16 around ROLEs
Next
From: Greg Sabino Mullane
Date:
Subject: Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC