Re: How to control pg_catalog results for each users?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: hirose shigeo(廣瀬 繁雄 □SWC○ACT) <shigeo(dot)hirose(at)toshiba(dot)co(dot)jp>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: How to control pg_catalog results for each users?
Date: 2023-01-30 05:48:51
Message-ID: 410287.1675057731@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sunday, January 29, 2023, hirose shigeo(廣瀬 繁雄 □SWC○ACT) <
> shigeo(dot)hirose(at)toshiba(dot)co(dot)jp> wrote:
>> Has there been any discussion or development on controlling this system
>> catalog information on a per-user

> I found this one:
> https://www.postgresql.org/message-id/flat/20160107032927.GT3685%40tamriel.snowman.net#6d9e59a0d052e7bdccd5a6c4e7a44a3f

There have been a ton of discussions around this area over the years.
The short answer is that if you think you need to prevent people
from seeing the contents of the system catalogs, Postgres is not
the database for you. I don't really foresee that changing, because
it would break at least as many use-cases as it would enable. The
thread David referenced only talks about side-effects on pg_dump,
but there are many other applications that would be just as broken
if we restricted this.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2023-01-30 08:41:53 Re: How to control pg_catalog results for each users?
Previous Message David G. Johnston 2023-01-30 05:23:54 Re: How to control pg_catalog results for each users?