Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension
Date
Msg-id CAFj8pRBmfASUwBzfmTjCJKRo-myJG+98MJmcZvKE-_fkLS277w@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers


2015-05-28 3:30 GMT+02:00 Joshua D. Drake <jd@commandprompt.com>:

On 05/27/2015 06:11 PM, Stephen Frost wrote:

Thank you for your honest comments and your concern.

I sincerely hope you're able to be involved in developing auditing for
PostgreSQL in the future, as it is a key requirement in any secure
environment.


Guys,

I think we are overlooking the rather obvious elephant in the room. This is an extension. There is no reason for it to be in core. Revert the patch, gain independence, the ability to innovate mid-cycle and move on to bigger fish.

any work in contrib has bigger progress.

I wrote plpgsql_check - and the living out of contrib is neutral  - I can do some changes freely, but it is used 1% users who can has benefit from this extension. 9.5 will be released after three months and lot  of potential bugs can be fixed. It is contrib - it can be moved, removed, but better if can works.

Regards

Pavel
 

Sincerely,

JD


--
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.



--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Sawada Masahiko
Date:
Subject: Re: Freeze avoidance of very large table.
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension