Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC - Mailing list pgsql-general

From Christophe Pettus
Subject Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC
Date
Msg-id 97788FFC-9F3D-43EC-BC76-AD695250C11A@thebuild.com
Whole thread Raw
In response to Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC  (Greg Sabino Mullane <htamfids@gmail.com>)
List pgsql-general

> On Sep 12, 2024, at 06:58, Greg Sabino Mullane <htamfids@gmail.com> wrote:
>
> But if it works for you, go ahead. As Tom said, it will work 95% of the time. But it will break things that should
work,and it will not prevent the ability to get the information in other ways. To be clear, we never recommend messing
withthe system catalogs, and this falls under the umbrella of messing with the system catalogs. 

I can only echo that if the compliance people are taking a position that "you need to make an unsupported, ad-hoc
modificationto the database software's authentication system in order to meet this requirement," then the requirement
isone that you should run, not walk, to get a waiver to, as that's a very unreasonable position for them to take. 


pgsql-general by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC
Next
From: Dominique Devienne
Date:
Subject: Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC