Re: PostgreSQL Auditing - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PostgreSQL Auditing
Date
Msg-id CA+TgmoYXn6cwm+fT6DnADyq_Y8g=rE=eSW9N2uSo-60-HTYUjQ@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Auditing  (Michael Banck <michael.banck@credativ.de>)
List pgsql-hackers
On Tue, Feb 2, 2016 at 11:13 AM, Michael Banck
<michael.banck@credativ.de> wrote:
> On Tue, Feb 02, 2016 at 07:24:23AM -0800, Joshua D. Drake wrote:
>> PostgreSQL has auditing. It is available now, just not in core. Postgis
>> isn't available in core either and it seems to do just fine.
>
> I don't really buy that argument. For one, PostGIS has a pretty narrow
> functional use-case (spatial), while auditing is a horizontal use-case
> that could be required for any kind of database usage.

If you're saying you think the user base for pgaudit will be larger
than the user base for PostGIS, color me doubtful.

> Now, whether or not the currently submitted approach actually meets the
> above rubber-stamp requirements is a different story, but at least I
> think it would be quite useful to ship auditing capabilites in the
> distribution.

That is a sensible position.  :-)

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: PostgreSQL Auditing
Next
From: Robert Haas
Date:
Subject: Re: RFC: replace pg_stat_activity.waiting with something more descriptive