Re: Restrict user to create only one db with a specific name

From: Paul Förster <paul(dot)foerster(at)gmail(dot)com>
To: Tiffany Thang <tiffanythang(at)gmail(dot)com>
Cc: Forums postgresql <pgsql-general(at)postgresql(dot)org>
Subject: Re: Restrict user to create only one db with a specific name
Date: 2020-03-07 07:35:22
Message-ID: 395AEEFA-8532-48E1-B1AA-8155DB162349@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Tiff,

from what you say, it sounds that each user should have his or her own database.

Considering the other answers here already pointing out the difficulties, why don't you just create a database for each user with the same name as the username and grant him or her access to it.

So, basically like this:

postgres=# create role "userA" login;
CREATE ROLE
postgres=# create database "userA" owner "userA";
CREATE DATABASE
postgres=# create role "userB" login;
CREATE ROLE
postgres=# create database "userB" owner "userB";
CREATE DATABASE

When, say, "userB" goes away, his or her data will go the way all things do:

drop database "userB";
drop role "userB";

Or did I misunderstand you?

Cheers,
Paul

> On 07. Mar, 2020, at 00:28, Tiffany Thang <tiffanythang(at)gmail(dot)com> wrote:
>
> Hi,
> Is there a way in PostgreSQL 12 to restrict user to creating a database with a specific database name?
>
> For example, userA can only create a database with a name called mydb. Any other names would generate an error.
>
> If that is not possible, will it be possible then to limit userA to creating only one database? Granting the createdb privilege would allow the user to create any number of databases which I want to avoid.
>
> Thanks.
>
> Tiff

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message stan 2020-03-07 11:56:15 Rules versus triggers
Previous Message David G. Johnston 2020-03-07 06:00:51 Re: Restrict user to create only one db with a specific name