Re: Effects of REVOKE SELECT ON ALL TABLES IN SCHEMA pg_catalog FROM PUBLIC
Andreas Joseph Krogh <andreas@visena.com>
From: Andreas Joseph Krogh <andreas@visena.com>
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-general@lists.postgresql.org
Date: 2024-09-12T13:21:49Z
Lists: pgsql-general
På torsdag 12. september 2024 kl. 15:05:48, skrev Greg Sabino Mullane < htamfids@gmail.com <mailto:htamfids@gmail.com>>: On Thu, Sep 12, 2024 at 12:52 AM Andreas Joseph Krogh <andreas@visena.com <mailto:andreas@visena.com>> wrote: I know PG is not designed for this, but I have this requirement nonetheless… I think preventing “most users and tools" from seeing/presenting this information is “good enough”. As pointed out, there are very many workarounds. This is security theater. Yes, it is theater, but that doesn't prevent “compliance people” to care about it. We have to take measures to prevent “information leaks”. -- Andreas Joseph Krogh CTO / Partner - Visena AS Mobile: +47 909 56 963 andreas@visena.com <mailto:andreas@visena.com> www.visena.com <https://www.visena.com> <https://www.visena.com>