X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 909409F9B76 for ; Thu, 4 May 2006 14:46:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 96034-06 for ; Thu, 4 May 2006 14:46:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from zixvpm01.seton.org (zixvpm01.seton.org [207.193.126.161]) by postgresql.org (Postfix) with ESMTP id 15CCD9FA7B6 for ; Thu, 4 May 2006 14:46:02 -0300 (ADT) Received: from zixvpm01.seton.org (ZixVPM [127.0.0.1]) by Outbound.seton.org (Proprietary) with ESMTP id DA45AA7D2B for ; Thu, 4 May 2006 12:46:00 -0500 (CDT) Received: from mx2-out.seton.org (unknown [10.21.254.241]) by zixvpm01.seton.org (Proprietary) with ESMTP id 6A755A7C94; Thu, 4 May 2006 12:46:00 -0500 (CDT) Received: from localhost (unknown [127.0.0.1]) by mx2-out.seton.org (Postfix) with ESMTP id 5D58D181D; Thu, 4 May 2006 12:46:00 -0500 (CDT) Received: from mx2-out.seton.org ([10.21.254.241]) by localhost (mx2 [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 03165-33; Thu, 4 May 2006 12:46:00 -0500 (CDT) Received: from ausexfe01.seton.org (ausexfe01.seton.org [10.20.10.211]) by mx2-out.seton.org (Postfix) with ESMTP id 3EBBB182B; Thu, 4 May 2006 12:46:00 -0500 (CDT) Received: from AUSEX3VS1.seton.org ([10.20.10.114]) by ausexfe01.seton.org with Microsoft SMTPSVC(6.0.3790.211); Thu, 4 May 2006 12:45:59 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: audit table containing Select statements submitted Date: Thu, 4 May 2006 12:45:59 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: audit table containing Select statements submitted Thread-Index: AcZu6VhYnvg1WdPBSDKKTAoR/p6KFQAuF5pg From: "Hogan, James F. Jr." To: , X-OriginalArrivalTime: 04 May 2006 17:45:59.0970 (UTC) FILETIME=[9AD56820:01C66FA2] X-Virus-Scanned: by amavisd-new at seton.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/182 X-Sequence-Number: 94974 No response from the pgsql-admin list so I though I would try cross posting here: pgsql-sql@postgresql.org pgsql-general@postgresql.org I just know I am not the first to try and do this=20 Jim ********************* Can anyone point me in a direction that may help me populate in real time a table that holds? Current_user Timestamp "The Select Statement Submitted by the User" I would like to easily determine who viewed what and when they viewed it. I have considered the fact that the result from SELECT yesterday may be different than the result set returned by the SAME SELECT statement today, but when used in conjunction with the INSERT, UPDATE, DELETE audit logging I have already created, the answers to who viewed, what and when would be readily available.=20 I have been searching all morning and... The only thing I find on logging of Select statements is that the information can be held in the Log Files...if Logging is enabled. =20 As I am only interested in the statements presented against certain tables... Turning on logging gives me more than I need or care to look through.=20 I could write a script to parses the Log Files into a Database Table but would prefer to avoid enabling the file logging of statements if possible. Thanks for any reference or help you may be able to provide. Jim