| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Neeraj M R <neerajmr12219(at)gmail(dot)com>, Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Restricting user to see schema structure |
| Date: | 2022-05-18 00:28:44 |
| Message-ID: | b2d5056c-399e-9d37-dd91-319a2094565a@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/17/22 13:21, Bryn Llewellyn wrote:
>
> The paragraph describes very surprising behavior in the present era of
> "secure by default". The sentence "For maximum security..." at the end
> emphasizes this and has you go to some effort (CREATE and REVOKE in the
> same txn) to undo the "insecurity by default" paradigm. I s'pose that
> compatibility on upgrade means that nothing can change here.
There is movement on this front coming in Postgres 15:
https://www.postgresql.org/docs/devel/release-15.html#id-1.11.6.5.3
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2022-05-18 01:47:13 | Re: Restricting user to see schema structure |
| Previous Message | David G. Johnston | 2022-05-17 20:45:24 | Re: Restricting user to see schema structure |