From: | CS DBA <cs_dba(at)consistentstate(dot)com> |
---|---|
To: | "M(dot) D(dot)" <lists(at)turnkey(dot)bz> |
Cc: | senthilnathan <senthilnathan(dot)t(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Read Only Role |
Date: | 2011-12-02 01:19:57 |
Message-ID: | 4ED827BD.4090103@consistentstate.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 11/30/2011 05:05 PM, M. D. wrote:
>
> On 11/29/2011 11:52 PM, senthilnathan wrote:
>> Is there any simple way to define read only roles. Basically that
>> user should
>> be able to login and be able to do *select* statements alone. It
>> should be
>> applied for all tables in all schemas in a database.
>>
>> --
>> View this message in context:
>> http://postgresql.1045698.n5.nabble.com/Read-Only-Role-tp5034628p5034628.html
>> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>>
> Google is your friend:
> http://stackoverflow.com/questions/760210/how-do-you-create-a-read-only-user-in-postgresql
>
>
>
I think you can do this:
ALTER USER [user] SET TRANSACTION READ ONLY;
--
---------------------------------------------
Kevin Kempter - Constent State
A PostgreSQL Professional Services Company
www.consistentstate.com
---------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-12-02 03:15:24 | Re: Upgrade from 9.0.5 to 9.1.1 - Problems with citext indexes |
Previous Message | Frank Lanitz | 2011-12-01 20:48:54 | Re: Use a custom postgresql.conf? |