Greetings,
Yes, you are correct. And
For applications/systems/scripts relying on this information may require
sgnificent modifications to handle the restricted access.
Alternative approches can be.
Auditing and monitoring.
You can use pgaudit extension for auditing and minitoring.
Use
Andreas Joseph Krogh writes:
> Hi, is there a way to prevent a user/role from SELECT-ing from certain
> system-tables?
> I'd like the contents of pg_{user,roles,database} to not be visible to all
> users.
As noted, you can in principle revoke the public SELECT grant from
those views/catalogs.
Greetings,
To prevent a user or role from selecting data from certain system tables in
PostgreSQL, you can revoke the default select permissions on those tables.
Here’s how you can do it:
1. Revoke SELECT permission on the system tables from the public role.
2. Grant SELECT permission only
Hi, is there a way to prevent a user/role from SELECT-ing from certain
system-tables?
I'd like the contents of pg_{user,roles,database} to not be visible to all
users.
Thanks.
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andr...@visena.com
Thanks Ron.
I did find one bug fix commit mentioning this error but it was saying that
was due to the interaction of two other commits that at least the first one
was after the cut of pg 12.2. so I have dismissed that as my deployment
issue.
I was looking for more evidence to push for a pg minor
On Thu, 2024-05-23 at 11:06 -0500, Skorpeo Skorpeo wrote:
> I see people are big fans of json here.
PostgreSQL's JSON support is great.
But way too often people use it in the wrong way.
Yours,
Laurenz Albe
On Thu, 2024-05-23 at 22:18 -0400, Tom Lane wrote:
> writes:
> > I've run into a strange issue with a unique index that I'm struggling to
> > understand. I've extracted the basic info to reproduce this below.
> > ...
> > This will now block until session 2 is complete. I don't understand why this
writes:
>> I've run into a strange issue with a unique index that I'm struggling
>> to understand. I've extracted the basic info to reproduce this below.
>> ...
>> This will now block until session 2 is complete. I don't understand
>> why this would block. I do know it's that unique index