From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Gabriel Muñoz <gabriel(dot)munoz(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: DBA user in Postgres |
Date: | 2012-11-28 21:16:51 |
Message-ID: | CAOR=d=2EFNL=VT2yaJD9vOH9sjUBYoosoJpqwk-_RAi5O_fNug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Nov 28, 2012 at 11:58 AM, Gabriel Muñoz <gabriel(dot)munoz(at)gmail(dot)com> wrote:
> 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.
If the db owner is steve, and you want bob to be able to do anything
steve can do, you can do:
grant steve to bob;
Does that do what you need?
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Crawford | 2012-11-28 22:09:37 | Re: Fwd: Monitoring Replication on Master/Slave Postgres(9.1) |
Previous Message | Kris Bushover | 2012-11-28 19:29:48 | Re: Fwd: Monitoring Replication on Master/Slave Postgres(9.1) |