| From: | John DeSoi <desoi(at)pgedit(dot)com> |
|---|---|
| To: | Andreas <maps(dot)on(at)gmx(dot)net> |
| Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Can I restrict backups? |
| Date: | 2007-05-23 12:24:56 |
| Message-ID: | 7A4AADFB-12E4-4F73-BA09-CC8BED4E3E17@pgedit.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On May 23, 2007, at 4:44 AM, Andreas wrote:
> Right.
> It's like that. They should work on projects that only contain a
> subset e.g. of customer addresses and subsequently on the task
> related objects like orders regarding the current project.
Another thought is to make all data returned through pl/pgsql
function calls (see SECURITY DEFINER option). I think you could
revoke all access to the underlying tables.
In addition to only returning data relevant to the task, the function
could automatically limit the number of rows returned to make it more
difficult to dump large amounts of data.
John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-05-23 13:38:26 | Re: initializing the DB cluster |
| Previous Message | Ireneusz Pluta | 2007-05-23 12:03:58 | Re: how to view all database,tables,users |