From: | Bryn Llewellyn <bryn(at)yugabyte(dot)com> |
---|---|
To: | 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>, Adrian Klaver <adrian(dot)klaver(at)aklaver(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 05:13:40 |
Message-ID: | E92A52A6-ACA5-4CDD-B65A-624A2B335E65@yugabyte.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> neerajmr12219(at)gmail(dot)com wrote:
>
> I am using pgAdmin . I have a database 'db' and it has got 2 schemas 'schema1' and 'schema2', I have created some views in schema2 from tables of schema1. I have created a new user and granted connection access to database and granted usage on tables and views of schema2 only. But now the problem is that the new user is able to see the table names of schema1 even though the user cannot see the data present in them they can see the table names. Is there any way I can completely hide schema1 from the new user.
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Neeraj M R | 2022-05-13 05:51:21 | Re: Restricting user to see schema structure |
Previous Message | David G. Johnston | 2022-05-13 05:08:51 | Re: Restricting user to see schema structure |