From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
---|---|
To: | "Little, Douglas" <DOUGLAS(dot)LITTLE(at)orbitz(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Auditing usage |
Date: | 2010-05-12 21:48:42 |
Message-ID: | AANLkTinqxp3WmqmoCv2gdudQAa3gG6Z-L_i3BaSEQTAJ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, May 12, 2010 at 2:36 PM, Little, Douglas
<DOUGLAS(dot)LITTLE(at)orbitz(dot)com>wrote:
> Is there anything in the system that would aid tracking who/how often an
> object (table/column/function/view) is accessed? In Teradata we have an
> accesslog table that record attempted access to an object and if it’s
> granted or denied. Very important to
>
>
This is the closed thing I've seen outside of scanning the postgresql logs.
http://www.depesz.com/index.php/2007/09/21/what-fields-are-usually-changed-when-updateing/
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-05-12 22:43:56 | Re: List traffic |
Previous Message | Little, Douglas | 2010-05-12 21:36:29 | Auditing usage |