| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com>, Neeraj M R <neerajmr12219(at)gmail(dot)com> |
| Cc: | Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Restricting user to see schema structure |
| Date: | 2022-05-13 15:30:30 |
| Message-ID: | 557fd2b6-dd2e-66ad-4920-25d173eaf10e@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/12/22 22:13, Bryn Llewellyn wrote:
>> /neerajmr12219(at)gmail(dot)com <mailto:neerajmr12219(at)gmail(dot)com> wrote:/
>>
> What exactly do you mean by "have created a new user and granted
> connection access to database"? As I understand it, there's no such
> thing. I mentioned a simple test in my earlier email that showed that
> any user (with no schema of its own and no granted privileges) can
> connect to any database—and see the full metadata account of all its
> content. I'm teaching myself to live with this.
Besides the REVOKE CONNECT, it is also possible to prevent connections
to a given database by a particular user by using settings in pg_hba.conf.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Niels Jespersen | 2022-05-13 16:25:21 | Logon via GSSAPI from Linux fails, but works from Windows |
| Previous Message | Adrian Klaver | 2022-05-13 15:16:25 | Re: Restricting user to see schema structure |