| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | PropAAS DBA <dba(at)propaas(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: system catalog permissions |
| Date: | 2018-02-26 23:47:41 |
| Message-ID: | 19827.1519688861@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
PropAAS DBA <dba(at)propaas(dot)com> writes:
> 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?
Messing with the system catalog permissions is likely to break stuff
you'd rather not break.
PG generally doesn't assume that anything in the system catalogs is
sensitive. If you don't want user A looking at user B's catalog
entries, give them separate databases, not just separate schemas.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Jungwirth | 2018-02-26 23:55:38 | Re: system catalog permissions |
| Previous Message | Joshua D. Drake | 2018-02-26 23:43:49 | Re: system catalog permissions |