Message-ID: <55243305.4050207@gmx.net>
Date: Tue, 07 Apr 2015 15:41:57 -0400
From: Peter Eisentraut <peter_e@gmx.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Alvaro Herrera <alvherre@2ndquadrant.com>,
 Simon Riggs <simon@2ndQuadrant.com>
CC: David Steele <david@pgmasters.net>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Auditing extension for PostgreSQL (Take 2)
References: <54E005CC.1060605@pgmasters.net> <5522EDE9.2050101@gmx.net>
 <CA+U5nMJnBbsDmxq7Dc6sz1orVQ9sZHpHz58N9oSc0yZLRGCfjw@mail.gmail.com>
 <20150406210357.GG4369@alvh.no-ip.org>
In-Reply-To: <20150406210357.GG4369@alvh.no-ip.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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