Re: Question about psql meta-command with schema option doesn't use visibilityrule - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Question about psql meta-command with schema option doesn't use visibilityrule
Date
Msg-id CAKFQuwYJvNF8xwpBeQE0PcLvQG_Y8cRACNyHi8Uuqvb7PFJTUw@mail.gmail.com
Whole thread Raw
In response to Question about psql meta-command with schema option doesn't use visibilityrule  (Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp>)
List pgsql-hackers
On Sunday, November 7, 2021, Tatsuro Yamada <tatsuro.yamada.tf@nttcom.co.jp> wrote:

According to the source code [1], there is no check if a schema
option is added. As a result, a role that is not granted can see
other roles' object names.
We might say it's okay because it's a name, not contents (data),
but It seems not preferable, I think.

No, we are not interested in changing this long-standing documented behavior.  The contents of the catalogs are visible to all.  So even if this was something to consider, psql is not the correct scope.

David J.

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: jsonb crash
Next
From: "David G. Johnston"
Date:
Subject: Re: Question about psql meta-command with schema option doesn't use visibilityrule