Role creation and management in PostgreSQL - Mini Project: Build & Apply

Role Creation and Management in PostgreSQL

📖 Scenario: You are a database administrator for a small company. You need to create roles to manage user permissions securely. This project will guide you through creating roles, assigning privileges, and managing role memberships in PostgreSQL.

🎯 Goal: Build a set of PostgreSQL commands to create roles, assign privileges, and manage role memberships to control database access effectively.

📋 What You'll Learn

Create a role named reporting_user without login permission

Create a role named data_analyst with login permission and password analyst123

Grant SELECT privilege on the sales table to reporting_user

Make data_analyst a member of reporting_user

Set data_analyst to inherit privileges from reporting_user

💡 Why This Matters

🌍 Real World

Database administrators use roles to control who can access and modify data securely in real companies.

💼 Career

Understanding role creation and management is essential for database security and user management in many IT and data-related jobs.

1

Create the reporting_user role

Create a role called reporting_user without login permission using the command CREATE ROLE reporting_user NOLOGIN;

PostgreSQL

# Create the reporting_user role without login permission
# Your code here

Hint

Use CREATE ROLE followed by the role name and NOLOGIN to prevent login.

2

Create the data_analyst role with login and password

Create a role called data_analyst with login permission and password analyst123 using CREATE ROLE data_analyst LOGIN PASSWORD 'analyst123';

PostgreSQL

CREATE ROLE reporting_user NOLOGIN;
# Create the data_analyst role with login and password
# Your code here

Hint

Use LOGIN to allow the role to connect and PASSWORD 'analyst123' to set the password.

3

Grant SELECT privilege on sales table to reporting_user

Grant SELECT privilege on the sales table to the role reporting_user using GRANT SELECT ON sales TO reporting_user;

PostgreSQL

CREATE ROLE reporting_user NOLOGIN;
CREATE ROLE data_analyst LOGIN PASSWORD 'analyst123';
# Grant SELECT privilege on sales table to reporting_user
# Your code here

Hint

Use GRANT SELECT ON sales TO reporting_user; to allow read access.

4

Make data_analyst a member of reporting_user and set inheritance

Make data_analyst a member of reporting_user using GRANT reporting_user TO data_analyst; and ensure data_analyst inherits privileges with ALTER ROLE data_analyst INHERIT;

PostgreSQL

CREATE ROLE reporting_user NOLOGIN;
CREATE ROLE data_analyst LOGIN PASSWORD 'analyst123';
GRANT SELECT ON sales TO reporting_user;
# Grant reporting_user role to data_analyst and set inheritance
# Your code here

Hint

Use GRANT reporting_user TO data_analyst; to add membership and ALTER ROLE data_analyst INHERIT; to allow privilege inheritance.

Practice

1. What is the primary purpose of a role in PostgreSQL?

easy

A. To control access and permissions for users and groups

B. To store data in tables

C. To create backups of the database

D. To optimize query performance

Solution

1. Step 1: Understand the concept of roles

   Roles in PostgreSQL are used to manage who can access the database and what they can do.

2. Step 2: Identify the main function of roles

   Roles control permissions and access rights, not data storage or backups.

3. Final Answer:

   To control access and permissions for users and groups -> Option A

4. Quick Check:

   Roles = Access control [OK]

Hint: Roles manage user permissions and access rights [OK]

Common Mistakes:

• Confusing roles with tables or data storage
• Thinking roles handle backups
• Assuming roles optimize queries

2. Which of the following is the correct syntax to create a role with login permission in PostgreSQL?

easy

A. CREATE ROLE user1 WITH LOGIN;

B. CREATE ROLE user1 CAN LOGIN;

C. CREATE ROLE user1 LOGIN;

D. CREATE ROLE user1 ALLOW LOGIN;

Solution

1. Step 1: Recall the syntax for creating a role with login

   The correct syntax uses WITH LOGIN to allow the role to log in.

2. Step 2: Check each option

   CREATE ROLE user1 WITH LOGIN; uses 'WITH LOGIN' which is correct. Others use incorrect keywords.

3. Final Answer:

   CREATE ROLE user1 WITH LOGIN; -> Option A

4. Quick Check:

   WITH LOGIN = enable login [OK]

Hint: Use WITH LOGIN to grant login rights when creating roles [OK]

Common Mistakes:

• Omitting WITH before LOGIN
• Using CAN or ALLOW instead of WITH
• Forgetting semicolon at end

3. Given the commands:

CREATE ROLE analyst NOLOGIN;
ALTER ROLE analyst CREATEDB;

What is true about the role analyst?

medium

A. The role can log in but cannot create databases

B. The role can log in and create databases

C. The role cannot log in but can create databases

D. The role cannot log in and cannot create databases

Solution

1. Step 1: Analyze the CREATE ROLE command

   The role 'analyst' is created with NOLOGIN, so it cannot log in.

2. Step 2: Analyze the ALTER ROLE command

   The role is altered to have CREATEDB permission, so it can create databases.

3. Final Answer:

   The role cannot log in but can create databases -> Option C

4. Quick Check:

   NOLOGIN + CREATEDB = no login, can create DB [OK]

Hint: NOLOGIN disables login; CREATEDB allows database creation [OK]

Common Mistakes:

• Assuming NOLOGIN means role cannot do anything
• Confusing CREATEDB with login permission
• Ignoring ALTER ROLE effects

4. Identify the error in the following command:

CREATE ROLE manager LOGIN PASSWORD 'secret';

medium

A. PASSWORD must be set using ENCRYPTED keyword

B. LOGIN cannot be used with PASSWORD

C. PASSWORD should be set with USING keyword

D. PASSWORD must be set using WITH keyword

Solution

1. Step 1: Check correct syntax for setting password

   In PostgreSQL, options like PASSWORD must be specified after WITH keyword.

2. Step 2: Identify the error in the command

   The command misses WITH before PASSWORD, causing syntax error.

3. Final Answer:

   PASSWORD must be set using WITH keyword -> Option D

4. Quick Check:

   Use WITH before PASSWORD [OK]

Hint: Use WITH before PASSWORD when creating roles [OK]

Common Mistakes:

• Omitting WITH before PASSWORD
• Thinking LOGIN disallows PASSWORD
• Using ENCRYPTED incorrectly

5. You want to create a role named developer that can log in, create databases, and also inherit permissions from another role team_member. Which command correctly achieves this?

hard

A. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT team_member;

B. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT team_member TO developer;

C. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; ALTER ROLE developer IN ROLE team_member;

D. CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT developer TO team_member;

Solution

1. Step 1: Create role with login, createdb, and inherit

   The role must be created with WITH LOGIN, CREATEDB, and INHERIT options.

2. Step 2: Grant membership to inherit permissions

   To inherit permissions from team_member, grant team_member role to developer using GRANT.

3. Step 3: Check each option

   CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT team_member TO developer; correctly creates the role and grants team_member to developer. Others misuse syntax or reverse grant direction.

4. Final Answer:

   CREATE ROLE developer WITH LOGIN CREATEDB INHERIT; GRANT team_member TO developer; -> Option B

5. Quick Check:

   GRANT role TO user for inheritance [OK]

Hint: Use GRANT role TO user to inherit permissions [OK]

Common Mistakes:

• Putting role name after INHERIT
• Reversing GRANT direction
• Missing WITH keyword or semicolon