Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 335071B505F1 for ; Wed, 14 Mar 2012 18:15:36 -0300 (ADT) Received: from plane.gmane.org ([80.91.229.3]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S7vXh-0000nz-4E for pgsql-admin@postgresql.org; Wed, 14 Mar 2012 21:15:36 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1S7vXT-0004Cr-1x for pgsql-admin@postgresql.org; Wed, 14 Mar 2012 22:15:19 +0100 Received: from cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com ([86.21.186.149]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Mar 2012 22:15:19 +0100 Received: from walterhurry by cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Mar 2012 22:15:19 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: Walter Hurry Subject: Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL Date: Wed, 14 Mar 2012 21:15:08 +0000 (UTC) Lines: 15 Message-ID: References: <8ecc4155e8754edef35e260a60a4a8db@mail.gmail.com> <1331722455.5503.166.camel@elliot> <98bfa47ff4bb6e222e89f751bbcbf4a7@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cpc3-walt15-2-0-cust148.13-2.cable.virginmedia.com User-Agent: Pan/0.135 (Tomorrow I'll Wake Up and Scald Myself with Tea; GIT 30dc37b master) X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201203/91 X-Sequence-Number: 39279 On Wed, 14 Mar 2012 13:24:36 +0200, Khangelani Gama wrote: > thanks, the issue we have is that we have many Linux users having root > access into the system. So they're able to access the DB by just going > in as "su - superusername". If this user is able to make any updates > inside the database it might create problems. Auditors wants PostgreSQL > to tell who updated what inside the database besides client users that > access the database from outside using some applications. So this common > "superusername" doesn't tell the actual person who got into the system > and went onto make updates inside the database because they first logged > as their linux users before as going in as postgres user called > "superusername". http://dl.dropbox.com/u/6106778/message.jpg