Re: Select Column Auditing/Logging

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Jeremy Brown <jwbrown77(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Select Column Auditing/Logging
Date: 2009-07-22 21:41:41
Message-ID: 1248298901.23273.16.camel@monkey-cat.sm.truviso.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2009-07-22 at 12:04 -0700, Jeremy Brown wrote:
> It seems that PostgreSQL can audit INSERT, UPDATE, DELETE, and
> TRUNCATE through the use of triggers. But SELECT triggers are
> unsupported (it does suggest perhaps using RULES).

One thing you can do is use a set-returning function that, as a side
effect, records what happened. It's not ideal because it hides a lot of
information from the optimizer, but if your table is small enough it
would work.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2009-07-22 21:44:29 Re: Select Column Auditing/Logging
Previous Message Andrew Klaassen 2009-07-22 21:14:23 table.column in query results?