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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Question about psql meta-command with schema option doesn't use visibilityrule
Date: 2021-11-08 03:09:44
Message-ID: CAKFQuwYJvNF8xwpBeQE0PcLvQG_Y8cRACNyHi8Uuqvb7PFJTUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, November 7, 2021, Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2021-11-08 03:40:21 Re: Question about psql meta-command with schema option doesn't use visibilityrule
Previous Message David Rowley 2021-11-08 02:47:58 Re: jsonb crash