Login vs group roles in PostgreSQL - Performance Comparison

Time Complexity: Login vs group roles

O(n)

Understanding Time Complexity

When checking user permissions in PostgreSQL, we often look at logins and group roles.

We want to understand how the time to verify permissions grows as the number of roles or groups increases.

Scenario Under Consideration

Analyze the time complexity of checking if a user belongs to a specific group role.

-- Check if user has the target_role directly
SELECT 1
FROM pg_auth_members m
JOIN pg_roles r ON m.roleid = r.oid
WHERE m.member = (SELECT oid FROM pg_roles WHERE rolname = 'username')
  AND r.rolname = 'target_role';
    

This query checks if 'username' is a direct member of 'target_role'.

Identify Repeating Operations

Look for repeated checks or loops in the query.

• Primary operation: Scanning membership links between users and roles.
• How many times: Once per membership record related to the user.

How Execution Grows With Input

As the number of group roles a user belongs to grows, the checks increase.

Input Size (number of roles/groups)	Approx. Operations
10	10 membership checks
100	100 membership checks
1000	1000 membership checks

Pattern observation: The number of checks grows linearly with the number of roles/groups.

Final Time Complexity

Time Complexity: O(n)

This means the time to check permissions grows in direct proportion to the number of roles or groups the user belongs to.

Common Mistake

[X] Wrong: "Checking group roles is instant and does not depend on how many groups a user has."

[OK] Correct: Each group membership must be checked, so more groups mean more work.

Interview Connect

Understanding how permission checks scale helps you design efficient access control in real systems.

Self-Check

"What if we cached group memberships for users? How would that change the time complexity?"

Practice

1. Which of the following best describes a login role in PostgreSQL?

easy

A. A role used only to group other roles without login capability.

B. A role that can connect to the database and perform actions.

C. A temporary session role that disappears after logout.

D. A role that automatically grants all permissions to users.

Solution

1. Step 1: Understand the purpose of login roles

   Login roles are created to allow users to connect to the database and perform tasks.

2. Step 2: Differentiate from group roles

   Group roles are for organizing users and sharing permissions but cannot login themselves.

3. Final Answer:

   A role that can connect to the database and perform actions. -> Option B

4. Quick Check:

   Login role = can connect [OK]

Hint: Login roles can connect; group roles cannot [OK]

Common Mistakes:

• Confusing group roles with login roles
• Thinking group roles can login
• Assuming login roles have no permissions

2. Which SQL command correctly creates a group role named managers without login capability?

easy

A. CREATE ROLE managers NOLOGIN;

B. CREATE ROLE managers LOGIN;

C. CREATE USER managers;

D. CREATE ROLE managers WITH LOGIN;

Solution

1. Step 1: Recall syntax for creating roles without login

   To create a group role, use CREATE ROLE with NOLOGIN option.

2. Step 2: Analyze options

   CREATE ROLE managers NOLOGIN; uses NOLOGIN correctly; options B and D enable login; CREATE USER managers; creates a login user.

3. Final Answer:

   CREATE ROLE managers NOLOGIN; -> Option A

4. Quick Check:

   Group role = NOLOGIN [OK]

Hint: Use NOLOGIN to create group roles [OK]

Common Mistakes:

• Using LOGIN when creating group roles
• Using CREATE USER instead of CREATE ROLE
• Omitting NOLOGIN for group roles

3. Given the following commands:

CREATE ROLE analysts NOLOGIN;
CREATE ROLE alice LOGIN PASSWORD 'secret';
GRANT analysts TO alice;

What is true about alice after these commands?

medium

A. Alice can login and has permissions of analysts role.

B. Alice cannot login because analysts role has NOLOGIN.

C. Alice can login but does not inherit analysts permissions.

D. Alice is a group role and cannot login.

Solution

1. Step 1: Understand role creation and grants

   Alice is a login role with password; analysts is a group role without login.

2. Step 2: Check role membership effect

   Granting analysts to alice means alice inherits analysts permissions and can login.

3. Final Answer:

   Alice can login and has permissions of analysts role. -> Option A

4. Quick Check:

   Login role + granted group role = login + permissions [OK]

Hint: Login roles inherit group role permissions when granted [OK]

Common Mistakes:

• Thinking NOLOGIN group role blocks login
• Assuming permissions are not inherited
• Confusing login and group roles

4. Identify the error in this SQL snippet:

CREATE ROLE developers;
CREATE ROLE bob LOGIN;
GRANT developers TO bob NOLOGIN;

medium

A. CREATE ROLE bob LOGIN is invalid syntax.

B. CREATE ROLE developers must include LOGIN.

C. Bob cannot be granted a role.

D. The GRANT statement incorrectly uses NOLOGIN.

Solution

1. Step 1: Review GRANT syntax

   GRANT role TO user does not accept NOLOGIN; NOLOGIN is for CREATE ROLE only.

2. Step 2: Check other statements

   CREATE ROLE developers is valid as group role; CREATE ROLE bob LOGIN is valid.

3. Final Answer:

   The GRANT statement incorrectly uses NOLOGIN. -> Option D

4. Quick Check:

   NOLOGIN only in CREATE ROLE, not GRANT [OK]

Hint: NOLOGIN is for CREATE ROLE, not GRANT [OK]

Common Mistakes:

• Adding NOLOGIN in GRANT statement
• Confusing role creation and granting syntax
• Assuming all roles must have LOGIN

5. You want to create a setup where multiple users share the same permissions easily. Which approach is best in PostgreSQL?

hard

A. Create only group roles and let users login as group roles.

B. Create multiple login roles with identical permissions separately.

C. Create individual login roles and grant them a common group role.

D. Create login roles and assign permissions directly to each.

Solution

1. Step 1: Understand permission management

   Group roles allow sharing permissions easily among many users.

2. Step 2: Evaluate options

   Create individual login roles and grant them a common group role. uses group roles granted to login roles, best for easy permission management.

3. Step 3: Reject incorrect options

   A is invalid as group roles cannot login; B duplicates permissions; D is less efficient.

4. Final Answer:

   Create individual login roles and grant them a common group role. -> Option C

5. Quick Check:

   Group roles + login roles = efficient permission sharing [OK]

Hint: Use group roles to share permissions among login roles [OK]

Common Mistakes:

• Trying to login as group roles
• Assigning permissions individually to each user
• Duplicating permissions instead of grouping