From: | Mija Lee <mija(at)scharp(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: thread by Jessica Richards on read only permissions |
Date: | 2007-10-27 00:09:32 |
Message-ID: | 472281BC.6020108@scharp.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Actually I didn't. I thought I had tried doing that as my testuser and
wasn't able to, but I must not have.
Okay, so nix that idea, because why assign security if it isn't secure.
Which brings me back to the question of if there is a way to do this
without listing every table in every schema. There must be...
Thanks Tom!
Mija
Tom Lane wrote:
> Mija Lee <mija(at)scharp(dot)org> writes:
>> I wanted to follow up on the thread opened by Jessica Richards on
>> granting read only permissions. Basically it sounded like there were two
>> options:
>
>> 1. granting select on each table
>> 2. alter user set default_transaction_read_only to true
>
> You do realize that #2 is completely insecure? It's only establishing a
> session default, which the user can override with a simple SET.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
From | Date | Subject | |
---|---|---|---|
Next Message | Oliveiros Cristina | 2007-10-29 15:36:51 | Graphical tools for PostGres |
Previous Message | Tom Lane | 2007-10-26 20:10:58 | Re: thread by Jessica Richards on read only permissions |