From: Stephen Frost <sfrost@snowman.net>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Fujii Masao <masao.fujii@gmail.com>
Cc: Sawada Masahiko <sawada.mshk@gmail.com>
Cc: David Steele <david@pgmasters.net>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Tatsuo Ishii <ishii@postgresql.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Abhijit Menon-Sen <ams@2ndquadrant.com>
Subject: Re: Auditing extension for PostgreSQL (Take 2)
Date: Mon, 4 May 2015 15:00:35 -0400
Message-ID: <20150504190035.GO30322@tamriel.snowman.net> (raw)
In-Reply-To: <55443ED1.6070003@gmx.net>
References: <552EA121.1090603@pgmasters.net>
<CAD21AoBoS6Q5yjB05LpfKTzhKmarqwwVq06fuPDFsm0T8gSk_Q@mail.gmail.com>
<5534FC6E.9030906@pgmasters.net>
<CAD21AoCxFOLWk-k179PyFxzwjkOW8oPaNk73GxZi+Yw2+n4YFA@mail.gmail.com>
<553938A1.7030707@pgmasters.net>
<CAD21AoDBt44ABM_0WMketM8bZtqLBMrJpd9RD5tE=Dkr57ft_A@mail.gmail.com>
<553FA477.5010803@pgmasters.net>
<CAD21AoCQSGZ5x+sfs4g1x_8Fip60x8ULQFTAGB5XTrKQZvPWPA@mail.gmail.com>
<CAHGQGwGJnRW69rSL1=tza571_eA44hBeChg-NAVrqQytESgvLg@mail.gmail.com>
<55443ED1.6070003@gmx.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
* Peter Eisentraut (peter_e@gmx.net) wrote:
> On 4/30/15 6:05 AM, Fujii Masao wrote:
> > The specification of "session audit logging" seems to be still unclear to me.
>
> As I had mentioned previously, I would prefer session audit logging to
> be integrated with the normal statement logging configuration.
I'd certainly love to see the logging in core be improved, but that's
also rather tangential to this extension and we could certainly have
both quite happily. Further, being able to configure and have
consistent information from the extension is valuable even if options
are added to the in-core logging to make it more flexible.
One particular advantage of having the extension is that having it
doesn't impact existing users of the in-core logging system. I don't
recall any specific proposals for improving the in-core logging system
to add the capabilities for session logging that the extension
provides, but it seems likely to require changes to at least the CSV
format, new log_line_prefix escape codes (which we're using quite a
few of already...), new GUCs, and potentially behavior changes to make
it work. As I say above, I'm happy to have those discussions (and
I've been party to them quite a few times in the past...), but it
seems unlikely to seriously reduce the usefulness of session logging
being in the extension and producing consistent output with the object
logging.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
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: sfrost@snowman.net, peter_e@gmx.net, masao.fujii@gmail.com, sawada.mshk@gmail.com, david@pgmasters.net, simon@2ndquadrant.com, ishii@postgresql.org, ams@2ndquadrant.com
Subject: Re: Auditing extension for PostgreSQL (Take 2)
In-Reply-To: <20150504190035.GO30322@tamriel.snowman.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