| From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgresql Developer Privileges |
| Date: | 2012-08-04 06:27:06 |
| Message-ID: | jvifbq$qn3$1@reversiblemaps.ath.cx |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2012-07-27, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 07/27/12 12:30 PM, hartrc wrote:
> and make each developer a member of this role.
>
>> Developers do not own the objects themselves
>
> thats a little more tricky, as AFAIK only a 'superuser' can change the
> role that owns an object, by default its owned by the rule that created
> it, but a user who's a member of a group can SET ROLE group; and then
> any objects they create belong to that group, or they can ALTER
> TABLE/VIEW/etc name OWNER TO newowner; for any role they are a member of.
>
after doing
grant developer to USERNAME;
you can do
alter user USERNAME set role to developer;
then when USERNAME logs it will be as if they had done
"set role to developer;"
--
⚂⚃ 100% natural
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2012-08-04 07:08:23 | Re: Installer problem report with interesting solution |
| Previous Message | Jasen Betts | 2012-08-04 05:07:29 | Re: Debian upgrade with PostgreSQL |