From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Andreas <maps.on@gmx.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Can I restrict backups?
Date: Tue, 22 May 2007 18:18:18 -0500
Message-ID: <46537A3A.3040709@g2switchworks.com> (raw)
In-Reply-To: <46523EF5.9020800@gmx.net>
References: <46523EF5.9020800@gmx.net>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: smarlowe@g2switchworks.com, maps.on@gmx.net
Subject: Re: Can I restrict backups?
In-Reply-To: <46537A3A.3040709@g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox