Re: Auditing extension for PostgreSQL (Take 2)

On 5/1/15 5:58 AM, Sawada Masahiko wrote:
> On Fri, May 1, 2015 at 6:24 AM, David Steele <david(at)pgmasters(dot)net> wrote:
>>
>> May 15th is the feature freeze, so that does give a little time. It's
>> not clear to me what a "self-contained" part of the patch would be. If
>> you have specific ideas on what could be broken out I'm interested to
>> hear them.
>>
>> Patch v11 is attached with the changes discussed here plus some other
>> improvements to the documentation suggested by Erik.
>>
>
> For now, since pg_audit patch has a pg_audit_ddl_command_end()
> function which uses part of un-committed "deparsing utility commands"
> patch API,
> pg_audit patch is completely depend on that patch.
> If API name, interface are changed, it would affect for pg_audit patch.
> I'm not sure about progress of "deparsing utility command" patch but
> you have any idea if that patch is not committed into 9.5 until May
> 15?

Currently the deparse dependent code is ifdef'd so pg_audit compiles and
operates just fine against master. Having the deparse code is nice
because it allows less common object types to log with full-qualified
names but it is in not a requirement for pg_audit.

I'd like to see at least patch 0001 of deparse committed. Not only
because it provides the functionality that deparse uses, but because it
makes event triggers truly useful in pl/pgsql.

--
- David Steele
david(at)pgmasters(dot)net