Subject: Re: future of pgaudit
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>,
 pgsql-admin@lists.postgresql.org
References: <9deda055-b59c-0755-2c29-3457d4d34968@matrix.gatewaynet.com>
From: David Steele <david@pgmasters.net>
Message-ID: <f18b34af-e7f9-4e59-58ae-480212218aef@pgmasters.net>
Date: Tue, 6 Mar 2018 08:13:41 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <9deda055-b59c-0755-2c29-3457d4d34968@matrix.gatewaynet.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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@pgmasters.net