pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hogan, James F. Jr. <JHogan@seton.org>
To: pgsql-sql@postgresql.org
To: pgsql-general@postgresql.org
Subject: audit table containing Select statements submitted
Date: Thu, 4 May 2006 12:45:59 -0500
Message-ID: <D73D467FE58F004E9D3FA25414945DC104FE0715@AUSEX3VS1.seton.org> (raw)

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 

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. 


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.  

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. 

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



view thread (2+ messages)  latest in thread

Message-ID: <D73D467FE58F004E9D3FA25414945DC104FE0715@AUSEX3VS1.seton.org>
Permalink:  ../D73D467FE58F004E9D3FA25414945DC104FE0715@AUSEX3VS1.seton.org/
Also on:    postgresql.org/message-id/D73D467FE58F004E9D3FA25414945DC104FE0715@AUSEX3VS1.seton.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: JHogan@seton.org, pgsql-general@postgresql.org
  Subject: Re: audit table containing Select statements submitted
  In-Reply-To: <D73D467FE58F004E9D3FA25414945DC104FE0715@AUSEX3VS1.seton.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox