Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 9D1781B505EF for ; Wed, 14 Mar 2012 10:40:01 -0300 (ADT) Received: from asbnvacz-mailrelay01.megapath.net ([207.145.128.243]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S7oQo-0008OH-6a for pgsql-admin@postgresql.org; Wed, 14 Mar 2012 13:40:00 +0000 Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.42]) by asbnvacz-mailrelay01.megapath.net (Postfix) with ESMTP id AAD29A70711 for ; Wed, 14 Mar 2012 09:39:42 -0400 (EDT) Received: (qmail 13754 invoked from network); 14 Mar 2012 13:39:42 -0000 Received: by simscan 1.4.0 ppid: 21470, pid: 14896, t: 1.1917s scanners: clamav: 0.88.2/m:52/d:10739 spam: 3.0.4 Received: from 205-168-220-157.dia.static.qwest.net (HELO [192.168.2.118]) (sribe@elevated-dev.com@[205.168.220.157]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 14 Mar 2012 13:39:40 -0000 Subject: Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Scott Ribe In-Reply-To: Date: Wed, 14 Mar 2012 07:39:39 -0600 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <7DF9BAC4-FAA7-459E-B5E2-6C5C732AB7FB@elevated-dev.com> References: <8ecc4155e8754edef35e260a60a4a8db@mail.gmail.com> <1331722455.5503.166.camel@elliot> 98bfa47ff4bb6e222e89f751bbcbf4a7@mail.gmail.com To: Khangelani Gama X-Mailer: Apple Mail (2.1084) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail3.sea5 X-Spam-Level: X-Spam-Status: No, score=0.0 required=8.0 tests=none autolearn=disabled version=3.0.4 X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201203/81 X-Sequence-Number: 39269 On Mar 14, 2012, at 6:39 AM, Khangelani Gama wrote: > ...the issue we have is that we have many Linux users having root > access into the system... Auditors wants PostgreSQL to tell who > updated what inside the database... Well, this is an obvious contradiction. You have an inherently = non-auditable setup that needs to be audited, and you're not going to = fix that with some magic setting somewhere. --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice