Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id BAE6F1337B9F for ; Tue, 4 Jan 2011 13:03:08 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 53537-05-4 for ; Tue, 4 Jan 2011 17:03:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.nextwavesys.com (fwbo.nextwavesys.net [64.151.139.178]) by mail.postgresql.org (Postfix) with ESMTP id 9D3D01337BB9 for ; Tue, 4 Jan 2011 13:03:01 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by mail.nextwavesys.com (Postfix) with ESMTP id A5A2F65F034 for ; Tue, 4 Jan 2011 12:04:56 -0500 (EST) X-Virus-Scanned: amavisd-new at nextwavesys.com Received: from mail.nextwavesys.com ([127.0.0.1]) by localhost (mail.nextwavesys.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yg6xahwsztbb for ; Tue, 4 Jan 2011 12:04:56 -0500 (EST) Received: from mail.nextwavesys.com (mail.nextwavesys.com [127.0.1.1]) by mail.nextwavesys.com (Postfix) with ESMTP id 3441465F056 for ; Tue, 4 Jan 2011 12:04:56 -0500 (EST) Date: Tue, 4 Jan 2011 12:04:56 -0500 (EST) From: Dan Sabin To: pgsql-admin@postgresql.org Message-ID: <24001946.1624.1294160696171.JavaMail.root@mail.nextwavesys.com> In-Reply-To: <13538541.1618.1294160668156.JavaMail.root@mail.nextwavesys.com> Subject: pgadmin user access control features MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.106.1] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Win)/6.0.7_GA_2473.DEBIAN5) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201101/34 X-Sequence-Number: 36474 Hello, So I plan on deploying a Postgres DB in an military project. On our admin end we are using the tool to help set up the database for delivery. Now the problem comes once the system is delivered. The database is used to record all the system messages for easy retrieval. This feature is rarely used and is only there if the system accidentally kills someone (Military grade security system with guns), the client needs to be able to reconstruct the event. In order to do this the client needs an interface to access the database. The two options are to give them a query tool we design so we can restrict their actions (to prevent the database from being screwed up). The other option would be to restrict their access in the pgadmin tool installed on the system itself and prevent them from deleting data. Is it possible to set up accounts within the tool and secure the admin access for ourselves so they can only run certain types of queries on their own account. I know this is possible with MS SQL Server tools, but we're bound to open source solutions. Any information would be useful. Thank you, Dan