| From: | Gabriel Muñoz <gabriel(dot)munoz(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | DBA user in Postgres |
| Date: | 2012-11-28 18:58:27 |
| Message-ID: | CAP8pxBZ03TcQQTbq9bt4fFQHnJK_MifBOQzpvdBcgDvHXMDstA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
As I can give you full permission to a user in a database. For everything
you have that database and the objects to be created in the future.
This means you can access all the schemes, all tables, views, functions, etc
.
If in the future you create a new view does not have to do a specific GRANT
to that user since the user is the "owner" of the database.
Try saying the user is super-user and restrict access only to the database
from pg_hba. But being super-user can for example delete another database that
is not theirs.
Thank you very much,
Gabriel.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2012-11-28 19:02:26 | Re: Fwd: Monitoring Replication on Master/Slave Postgres(9.1) |
| Previous Message | Gabriel Muñoz | 2012-11-28 18:46:07 | Re: NEED REPLICATION SOLUTION -POSTGRES 9.1 |