From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: future of pgaudit |
Date: | 2018-03-06 13:17:38 |
Message-ID: | bd614621-3556-5b89-6f4f-4967d4a49f8d@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Good Day David!
On 06/03/2018 15:13, David Steele wrote:
> Hello Achilleas,
>
> On 3/6/18 6:00 AM, Achilleas Mantzios wrote:
>> Just found https://github.com/pgaudit/pgaudit and my boss seemed excited.
>> However then I saw this : https://github.com/2ndQuadrant/pgaudit
> pgaudit was originally forked from a 2nd Quadrant project that has since
> been deprecated. The repo you see at 2nd Quadrant now is a fork that
> has not been kept up to date with the main repo,
>
>> and then again this :
>> "New development, if any, will be strictly for next unreleased major
>> version of PostgreSQL."
> We don't add features every year because the primary goal is stability.
>
>> This "if any" part put me into some thoughts. Is there intention to keep
>> supporting this?
> pgaudit is actively maintained, but other than rare bugs fixes it is
> generally updated just once a year for each new version of PostgreSQL.
>
> It's safe to say that pgaudit will be around for the foreseeable future.
Thank you for your answer!
>
> Regards,
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
From | Date | Subject | |
---|---|---|---|
Next Message | Fabio Pardi | 2018-03-06 13:26:58 | Re: Finding out the aging tables for vacuuming to prevent data loss on transaction id wraparound |
Previous Message | David Steele | 2018-03-06 13:13:41 | Re: future of pgaudit |