From: Peter Eisentraut <peter_e@gmx.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: David Steele <david@pgmasters.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Auditing extension for PostgreSQL (Take 2)
Date: Tue, 07 Apr 2015 15:41:57 -0400
Message-ID: <55243305.4050207@gmx.net> (raw)
In-Reply-To: <20150406210357.GG4369@alvh.no-ip.org>
References: <54E005CC.1060605@pgmasters.net>
<5522EDE9.2050101@gmx.net>
<CA+U5nMJnBbsDmxq7Dc6sz1orVQ9sZHpHz58N9oSc0yZLRGCfjw@mail.gmail.com>
<20150406210357.GG4369@alvh.no-ip.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 4/6/15 5:03 PM, Alvaro Herrera wrote:
> 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.
Well, this one is the commitfest thread of record.
At quick glance, my comments about "how does this map to specific
customer requirements" apply to the other submission as well.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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-hackers@postgresql.org
Cc: peter_e@gmx.net, alvherre@2ndquadrant.com, simon@2ndQuadrant.com, david@pgmasters.net
Subject: Re: Auditing extension for PostgreSQL (Take 2)
In-Reply-To: <55243305.4050207@gmx.net>
* 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