| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Chirag Karkera <chiragkrkr102(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Provide read-only access to system catalog tables |
| Date: | 2022-05-17 13:29:31 |
| Message-ID: | CAKFQuwYOfH3Gr3XB3Waf1gM6xn9ntZ6_mc6mwOiw=-6531S=tQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 17, 2022 at 6:21 AM Chirag Karkera <chiragkrkr102(at)gmail(dot)com>
wrote:
> Thanks David for your reply!
>
> But when i created a role i am not able to view objects under
> information_schema.*
>
> I mean I am not able to view the data, I can see only the column names.
>
>>
>>
Which goes to demonstrate you have permissions. But information_schema
uses the permissions of the executing user to decide what to show - it is
pre-filtered (and doesn't address PostgreSQL-only features). If you need
less restrictive behavior your best bet is to just use the system
catalogs. Those give you everything.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2022-05-17 13:33:57 | Re: Avoid unecessary MemSet call (src/backend/utils/cache/relcache.c) |
| Previous Message | Chirag Karkera | 2022-05-17 13:21:03 | Re: Provide read-only access to system catalog tables |