On Wed, Jul 22, 2009 at 02:41:41PM -0700, Jeff Davis wrote:
> 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 R
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, a
On Wed, 2009-07-22 at 14:41 -0700, Jeff Davis wrote:
> 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).
Hello,
I've tried searching around the net for a feature that would allow me to audit
to a table or log select queries against a certain column in a table. In fact,
I haven't been able to find a way to log selects to a specific table, just
logging all queries.
It seems that PostgreSQL can au
