Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YqScx-0003x6-K6 for pgsql-hackers@arkaria.postgresql.org; Thu, 07 May 2015 20:42:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YqScw-0003Gy-Ps for pgsql-hackers@arkaria.postgresql.org; Thu, 07 May 2015 20:42:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YqScv-0003Gq-Lr for pgsql-hackers@postgresql.org; Thu, 07 May 2015 20:42:37 +0000 Received: from mout.gmx.net ([212.227.17.20]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84) (envelope-from ) id 1YqScr-0003xQ-De for pgsql-hackers@postgresql.org; Thu, 07 May 2015 20:42:36 +0000 Received: from auth1-smtp.messagingengine.com ([66.111.4.227]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MPZuP-1YubUE1eEL-004nCg for ; Thu, 07 May 2015 22:42:31 +0200 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailauth.nyi.internal (Postfix) with ESMTP id 021AB20C3A for ; Thu, 7 May 2015 16:42:27 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 07 May 2015 16:42:28 -0400 X-Sasl-enc: LBkXCA+RIsUdGhAUYe5qWPPisqKfC2agnXBJJYep9/id 1431031347 Received: from [192.168.1.147] (unknown [204.145.120.11]) by mail.messagingengine.com (Postfix) with ESMTPA id D0744680081; Thu, 7 May 2015 16:42:26 -0400 (EDT) Message-ID: <554BCE32.7010709@gmx.net> Date: Thu, 07 May 2015 16:42:26 -0400 From: Peter Eisentraut User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Stephen Frost CC: Fujii Masao , Sawada Masahiko , David Steele , Simon Riggs , Tatsuo Ishii , PostgreSQL-development , Abhijit Menon-Sen Subject: Re: Auditing extension for PostgreSQL (Take 2) References: <553938A1.7030707@pgmasters.net> <553FA477.5010803@pgmasters.net> <55443ED1.6070003@gmx.net> <20150504190035.GO30322@tamriel.snowman.net> <5548095A.1040900@gmx.net> <20150505003719.GQ30322@tamriel.snowman.net> <5549172B.70005@gmx.net> <20150507142655.GW30322@tamriel.snowman.net> In-Reply-To: <20150507142655.GW30322@tamriel.snowman.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:XGDs08mHewTjgOvTgu3lcEXQg7SLjHYkiF2eB+c5GRoNi6jJWW4 IXQ9U9b+nG3PYu6/B8WLnoDFm68nRjbY3KUZiJ0Cza38t5s9UeUjIOa/lhTbPDny4Tnq85I cGgWEKKuU8oWGC6Uk2r5nx7DQ05ovkPg8ScOon2pU9BOAlMjg5ZxahXy+T0O5HzCIYxzzcS 4Y1byVJTp6crgJeLpd1UA== X-UI-Out-Filterresults: notjunk:1; X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 5/7/15 10:26 AM, Stephen Frost wrote: > Auditing is about "what happened" whereas > statement logging is "log whatever statement the user sent." pgAudit > bears this out by logging internal SQL statements and object > information, unlike what we do with statement logging today. I don't think this is quite correct. For example, log_min_duration_statement logs based on what happened. log_duration records what happened. log_checkpoints records what happened. log_statement also requires parsing before deciding whether to log. Generally, "logging" is "what happened". The stuff in syslog is what happened on the system. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers