Re: Auditing extension for PostgreSQL (Take 2)

Simon Riggs wrote:

> The present version can trigger an audit trail event for a statement,
> without tracking the object that was being audited. This prevents you
> from searching for "all SQL that touches table X", i.e. we know the
> statements were generated, but not which ones they were. IMHO that
> makes the resulting audit trail unusable for auditing purposes. I
> would like to see that functionality put back before it gets
> committed, if that occurs.

Is there a consensus that the current version is the one that we should
be reviewing, rather than the one Abhijit submitted?  Last I checked,
that wasn't at all clear.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services