| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Auditing extension for PostgreSQL (Take 2) |
| Date: | 2015-04-06 21:03:57 |
| Message-ID: | 20150406210357.GG4369@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-04-06 21:17:24 | Re: BRIN range operator class |
| Previous Message | Simon Riggs | 2015-04-06 20:47:01 | Re: Auditing extension for PostgreSQL (Take 2) |