Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 620A19FB6A7 for ; Tue, 22 May 2007 20:18:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 46403-05 for ; Tue, 22 May 2007 20:18:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id B98F49FB6A1 for ; Tue, 22 May 2007 20:18:23 -0300 (ADT) Received: from [10.10.1.37] ([10.10.1.37]) by exchange.g2switchworks.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 May 2007 18:18:18 -0500 Message-ID: <46537A3A.3040709@g2switchworks.com> Date: Tue, 22 May 2007 18:18:18 -0500 From: Scott Marlowe User-Agent: Thunderbird 1.5.0.4 (X11/20060516) MIME-Version: 1.0 To: Andreas CC: pgsql-admin@postgresql.org Subject: Re: Can I restrict backups? References: <46523EF5.9020800@gmx.net> In-Reply-To: <46523EF5.9020800@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 May 2007 23:18:18.0320 (UTC) FILETIME=[7B3A6D00:01C79CC7] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/230 X-Sequence-Number: 25550 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.