Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YpiLA-0003DY-MV for pgsql-hackers@arkaria.postgresql.org; Tue, 05 May 2015 19:17:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YpiLA-000512-2W for pgsql-hackers@arkaria.postgresql.org; Tue, 05 May 2015 19:17:12 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YpiL9-00050w-5r for pgsql-hackers@postgresql.org; Tue, 05 May 2015 19:17:11 +0000 Received: from mout.gmx.net ([212.227.15.18]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84) (envelope-from ) id 1YpiL2-0006hq-BE for pgsql-hackers@postgresql.org; Tue, 05 May 2015 19:17:09 +0000 Received: from auth1-smtp.messagingengine.com ([66.111.4.227]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LpsIh-1ZUnec3TDL-00fhSD for ; Tue, 05 May 2015 21:17:02 +0200 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id 53E6A21D94 for ; Tue, 5 May 2015 15:17:00 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 05 May 2015 15:17:00 -0400 X-Sasl-enc: EcMLi7o/ovi7U636c5ul2865P/cWGcPt73u4DgJM1MQz 1430853420 Received: from [192.168.1.147] (unknown [204.145.120.11]) by mail.messagingengine.com (Postfix) with ESMTPA id 0D1F86800CC; Tue, 5 May 2015 15:17:00 -0400 (EDT) Message-ID: <5549172B.70005@gmx.net> Date: Tue, 05 May 2015 15:16:59 -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: <5534FC6E.9030906@pgmasters.net> <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> In-Reply-To: <20150505003719.GQ30322@tamriel.snowman.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:QrvM6o5ZL/TOX936KHsb4fc6Xy0UjE7QrsXCtvMjn56KLIsuS11 8gO0auBpdQQQxhppNfxLgj3AREvdpJGySFvo1hRlaGX1IOAUygQ0htzy35KT5l/O1IiYWIu +x00QxHmbR5nbTG+4/Jiu9chcmcDmEs5oj0uCOyUE4YENKZulW6HOKk9m3ddZgMDF1/jXHc XlcyBBv/pNu3BUd6/uyJQ== 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/4/15 8:37 PM, Stephen Frost wrote: > I don't follow this logic. The concerns raised above are about changing > our in-core logging. We haven't got in-core auditing and so I don't see > how they apply to it. How is session "auditing" substantially different from statement logging? I think it is not, and we could tweak the logging facilities a bit to satisfy the audit trail case while making often-requested enhancement to the traditional logging use case as well at the same time. At least no one has disputed that yet. The only argument against has been that they don't want to touch the logging. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers