From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | venkatesh R <venkatesh(dot)ramanujam007(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: PG Role : With Crud Operations without Drop DB user |
Date: | 2024-02-28 03:45:39 |
Message-ID: | CAKFQuwYJcdn-2viKwA6ZuwsJecWTbh1b70hcVWkOoxzy67JPLA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Feb 27, 2024 at 8:30 PM venkatesh R <
venkatesh(dot)ramanujam007(at)gmail(dot)com> wrote
> REVOKE CREATE, DROP ON ALL TABLES IN SCHEMA public FROM developer;REVOKE CREATE, DROP ON ALL SCHEMAS IN DATABASE your_database_name FROM developer;
>
>
What exactly are you using here? There is no DROP permission and CREATE
doesn't apply to tables.
> The commands we used are still able to drop the database. Which it
> shouldn't do.
>
I don't see either a create database nor a drop database command in that so
it is hard to say where you are going wrong. I suggest you write a
self-contained psql script demonstrating explicitly the problematic
behavior. A randomly created role that is neither a superuser nor the
database owner will be unable to drop a database.
Is this possible in Postgres, we have tried all the commands.
>
>
> Apparently including some that don't even exist...
Write a script, we don't care about permutations, choose your best guess,
that doesn't have non-permission related errors i.e., no syntax problems or
command not found. Then ask why that script does or doesn't behave in some
way surprising to you.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar | 2024-02-28 06:01:21 | Mean_exec_time |
Previous Message | venkatesh R | 2024-02-28 03:30:07 | PG Role : With Crud Operations without Drop DB user |