| From: | Kenneth Downs <ken(at)secdat(dot)com> |
|---|---|
| To: | David Legault <legault(dot)david(at)gmail(dot)com>, Kenneth Downs <ken(at)secdat(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: HIPPA (was Re: Anyone know ...) |
| Date: | 2007-03-10 20:21:41 |
| Message-ID: | 45F31355.1050104@secdat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera wrote:
> David Legault escribió:
>
>> That's basically what I've done with my past questions on the ROLE system in
>> place. Since roles are global, I wanted it fine grained to the DB level so I
>> had to append DB_ in front of each role name and by using current_database()
>> inside my functions, I could hide that from the exterior.
>>
>
> Hmm, there used to be a facility to restrict users to specific
> databases, enabled by db_user_namespace (not by default).
>
> It seems to still work on 8.2 ...
>
>
there is also the 'samegroup' facility in pg_hba.conf. We create a
group named after each database, and a person cannot get into a database
unless they are in that group.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-03-10 20:47:36 | Re: How to enforce uniqueness when NULL values are present? |
| Previous Message | Alvaro Herrera | 2007-03-10 20:14:33 | Re: HIPPA (was Re: Anyone know ...) |