From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | PropAAS DBA <dba(at)propaas(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: system catalog permissions |
Date: | 2018-02-26 23:43:49 |
Message-ID: | b164f3c7-91a5-7c19-7b93-5d87b2eb2750@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/26/2018 03:11 PM, PropAAS DBA wrote:
> All;
>
>
> We have a client which is segmenting their multi-tenant cluster
> (PostgreSQL 9.6) by schema, however if one of their clients connects
> via pgadmin they see ALL schemas, even the ones they don't have access
> to read. I assume pgadmin is pulling the list from the system catalogs.
>
>
> What's the right/best practice approach? revoke all from public on
> specific system catalog tables? Which tables?
AFAIK, you can not hide the list of schemas but you can prevent people
from entering them.
JD
>
>
> Thanks in advance
>
>
--
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
***** Unless otherwise stated, opinions are my own. *****
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-02-26 23:47:41 | Re: system catalog permissions |
Previous Message | PropAAS DBA | 2018-02-26 23:11:23 | system catalog permissions |