Re: Provide read-only access to system catalog tables

From: Chirag Karkera <chiragkrkr102(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(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 14:07:34
Message-ID: CANZL2iHF9w69A1fQJ53srATAAX=oHjfHaVFLH7py9mS4G2Zo9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you for the clarification.

Will use the system catalogs tables.

Thank You.

Regards,
Chirag Karkera

On Tue, May 17, 2022 at 6:59 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> 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.
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ronan Dunklau 2022-05-17 14:14:46 Re: Removing unneeded self joins
Previous Message Jonathan S. Katz 2022-05-17 13:58:14 Re: PostgreSQL 15 Beta 1 release announcement draft