| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: future of pgaudit |
| Date: | 2018-03-06 13:13:41 |
| Message-ID: | f18b34af-e7f9-4e59-58ae-480212218aef@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2018-03-06 13:17:38 | Re: future of pgaudit |
| Previous Message | Subramanian Krishnan | 2018-03-06 11:54:18 | Re: Finding out the aging tables for vacuuming to prevent data loss on transaction id wraparound |