Re: Define permissions at database level

From: dipti shah <shahdipti1980(at)gmail(dot)com>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Define permissions at database level
Date: 2010-02-18 11:09:06
Message-ID: d5b05a951002180309w129ebf7fnda69b3bb7a0bf6b4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-novice

Thanks. I will do testing.

On Thu, Feb 18, 2010 at 4:29 PM, Richard Huxton <dev(at)archonet(dot)com> wrote:

> On 18/02/10 10:54, dipti shah wrote:
>
>> Okay then I think below works:
>>
>> 1. Revoke permission ALL permissions from PUBLIC on schema.
>>
>> REVOKE ALL ON ALL TABLES IN SCHEMA mySchema FROM PUBLIC;
>>
>> 2. Give store procedure for creating table with SECURITY DEFINER marked
>> so that all tables owner will be "postgres" user.
>> 3. Grant SELECT permission to required group on created table.
>> 4. Give store procedure for droping the table with SECURITY DEFINER
>> marked so that droping will happen in the context of "postgres" user.
>>
>> I think above will not allow anyone to create and/or drop tables directly
>> without using store procedures.
>>
>> Please let me know if I am missing anything.
>>
>
> Sounds about right. Always test though.
>
> --
> Richard Huxton
> Archonet Ltd
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message wilczarz1 2010-02-18 12:05:57 PERFORM not working properly, please help..
Previous Message Richard Huxton 2010-02-18 10:59:43 Re: Define permissions at database level

Browse pgsql-novice by date

  From Date Subject
Next Message Didier Gasser-Morlay 2010-02-18 14:53:20 reporting and transposition
Previous Message Richard Huxton 2010-02-18 10:59:43 Re: Define permissions at database level