[Solved] Why does PostgreSQL use roles instead of separate user and group concepts for permissions? — Ans: Roles unify users and groups for simpler permission management | PostgreSQL

PostgreSQL - Roles and Security

Why does PostgreSQL use roles instead of separate user and group concepts for permissions?

ARoles are only for database administrators

BRoles are deprecated in favor of users and groups

CRoles cannot have login privileges

DRoles unify users and groups for simpler permission management

Step-by-Step Solution

Solution:

Step 1: Understand PostgreSQL role concept
PostgreSQL uses roles to combine user and group features into one entity.
Step 2: Analyze options
Roles unify users and groups for simpler permission management correctly states that roles unify users and groups to simplify permission management.
Final Answer:
Roles unify users and groups for simpler permission management -> Option D
Quick Check:
Roles = unified users and groups [OK]

Quick Trick: Roles combine user and group features in PostgreSQL [OK]

Common Mistakes:

Master "Roles and Security" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Why does PostgreSQL use roles instead of separate user and group concepts for permissions?