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 Dominique Devienne
Subject Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC
Date
Msg-id CAFCRh-_8P=Se_4F5VXn=Z9vc5Dj6+k+xd7HGtt5zsg_=Ltqiyw@mail.gmail.com
Whole thread Raw
In response to Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC  (Greg Sabino Mullane <htamfids@gmail.com>)
List pgsql-general
Tree view 
On Thu, Sep 12, 2024 at 3:53 PM Greg Sabino Mullane <htamfids@gmail.com> wrote:
> 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: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  role "eve" does not exist
> psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  database "theater" does not exist
> psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL:  password authentication failed for
user"alice" 

Ah silly me, I was thinking of something else.
Sure, "probing" for DB or USER names by attempting connecting is of
course an option.
Thanks, --DD

pgsql-general by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC
Next
From: Tom Lane
Date:
Subject: Re: RLS and Table Inheritance