| From: | hirose shigeo(廣瀬 繁雄 □SWC○ACT) <shigeo(dot)hirose(at)toshiba(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-31 09:31:43 |
| Message-ID: | 2e2409c4-f45e-6c99-5366-1d81aba2cd69@swc.toshiba.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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.
Thank you for information.
I understood community's concern and policy.
Regards,
Shigeo Hirose
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Max Nikulin | 2023-01-31 11:32:09 | Re: timestamptz, local time in the future, and Don't do it wiki |
| Previous Message | qihua wu | 2023-01-31 08:22:10 | Re: any wait event for a commit in sync replication? |