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:40:21
Message-ID: CAKFQuwYb5ajUkc-XVxXtcgCoh5ALe9dHKyOscQ=qSvAV_qpUWQ@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:

>
> I have a question that is a specification of permission check
> (visibilityrule) for psql meta-command with schema option.
>
> From the above results, I expected "\dX s_a.*" doesn't show any info
> as same as "\dX". but info is displayed. I'm wondering this behavior.
>
> I'm maybe missing something, but if this is a problem, I'll send a
> patch. Any comments are welcome!
>
>
Visibility means search_path, not permission. If s_a is not in the
search_paths it objects are not visible unqualified but can be seen
(catalog) when schema qualified.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-11-08 03:53:58 Re: pg_upgrade test for binary compatibility of core data types
Previous Message David G. Johnston 2021-11-08 03:09:44 Re: Question about psql meta-command with schema option doesn't use visibilityrule