[Solved] You wrote this command to restrict user access:REVOKE SELECT ON employees FROM guest_user;But guest_user still can SELECT data. What is the likely problem? | PostgreSQL

PostgreSQL - Roles and Security

You wrote this command to restrict user access:
REVOKE SELECT ON employees FROM guest_user;
But guest_user still can SELECT data. What is the likely problem?

Aguest_user has SELECT permission through a role or group

BREVOKE command syntax is incorrect

Cguest_user is the database owner

DSELECT permission cannot be revoked

Step-by-Step Solution

Solution:

Step 1: Understand REVOKE command effect
REVOKE removes direct permissions from a user but does not affect permissions inherited from roles or groups.
Step 2: Identify why guest_user still has access
If guest_user belongs to a role or group with SELECT permission, they keep access despite the REVOKE.
Final Answer:
guest_user has SELECT permission through a role or group -> Option A
Quick Check:
Inherited permissions override REVOKE [OK]

Quick Trick: Check roles/groups for inherited permissions [OK]

Common Mistakes:

Assuming REVOKE always removes access
Thinking syntax is wrong without checking
Believing owners cannot lose permissions

Master "Roles and Security" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

You wrote this command to restrict user access:

Step 1: Understand REVOKE command effect

Step 2: Identify why guest_user still has access

Final Answer:

Quick Check:

Want More Practice?