| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Grant all privileges to user on a database |
| Date: | 2023-07-24 14:59:35 |
| Message-ID: | CAKFQuwZAqTAcqbsC1vWT6rX4FX13ebLwqLURv6m0QeMOi-RguQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 24, 2023 at 7:52 AM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> On 7/24/23 09:09, Tom Lane wrote:
>
> > GRANT ALL ON SCHEMA public TO public;
>
> I'd have naively expected "GRANT ALL ON SCHEMA public TO public; " to be
> taken care of by "GRANT ALL PRIVILEGES ON DATABASE cbdevdb TO
> cbdevdbadmin;".
>
>
I'm quite happy that such a command doesn't go ahead and grant read, write,
and execute privileges on every table, function, and view in the database.
The thing that does what you describe is called SUPERUSER.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-07-24 15:58:50 | Re: How to improve the performance of my SQL query？ |
| Previous Message | David G. Johnston | 2023-07-24 14:56:02 | Re: [Beginner Question]Is there way to test the postgres's kernel function? |