{"id":27606,"date":"2023-09-05T14:45:14","date_gmt":"2023-09-05T12:45:14","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=27606"},"modified":"2023-09-05T14:45:16","modified_gmt":"2023-09-05T12:45:16","slug":"create-user-create-role-what-should-be-used-in-postgresql","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/create-user-create-role-what-should-be-used-in-postgresql\/","title":{"rendered":"“create user”, “create role”, what should be used in PostgreSQL?"},"content":{"rendered":"\n

Recently we’ve seen a video on YouTube which recommends not to use the “create user” command in PostgreSQL and instead always use the “create role” command. It was also mentioned that “create group” should not be used as well. We’ve been a bit surprised by this and this is the reason for this post.<\/p>\n\n\n\n

While we never use the “create group” command, there is nothing in the documentation<\/a> which recommends to avoid it. What is written there is, that “create group” is an alias for “create role”. This changed in version 8.1 of PostgreSQL and if you take a look at the release notes <\/a>you will find this: <\/p>\n\n\n\n

“Create a new role system that replaces users and groups (Stephen Frost)<\/p>\n\n\n\n

Roles are a combination of users and groups. Like users, they can have login capability, and like groups, a role can have other roles as members. Roles basically remove the distinction between users and groups. For example, a role can:<\/p>\n\n\n\n