| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> | 
|---|---|
| To: | Andreas <maps(dot)on(at)gmx(dot)net> | 
| Cc: | pgsql-admin(at)postgresql(dot)org | 
| Subject: | Re: Can I restrict backups? | 
| Date: | 2007-05-22 23:18:18 | 
| Message-ID: | 46537A3A.3040709@g2switchworks.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin | 
Andreas wrote:
> Hi,
> now this might be a bit of a silly question, but I'll give it a shot 
> anyway.
>
> I'm working on a remote database for a few employees of a rather small 
> startup company where at least a few will get teleworking jobs. 
> They'll get a ms-access application that connects via ODBC from their 
> home.
>
> They'll have limited access to the tables. Some will be just readable 
> or writable.
> Obviously to work with the most intersting data they'll need reading 
> an writing access.
>
> Could I somehow avoid that one of them uses pg_dump or even Access 
> itself to pull all the data out and sell it to a competitor? 
You have conflicting objectives here.
You give them read access to the data, but you don't want them to read it.
The real issue here is a legal one.  Once you let the data go from the 
server to their machine, who knows what they'll do with it. 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Islam Hegazy | 2007-05-23 05:44:51 | initializing the DB cluster | 
| Previous Message | Peter Koczan | 2007-05-22 21:05:30 | Re: trouble restarting a server |