Message-ID: <61c23ed4.1c69fb81.e4f24.27ac@mx.google.com>
Date: Tue, 21 Dec 2021 21:53:39 +0100
From: Michael Banck <michael.banck@credativ.de>
To: Daulat <daulat.dba@gmail.com>
Cc: Holger Jakobs <holger@jakobs.com>,
	pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: How to Log DBA actions
References: 
 <CALfOM6LVK2cPspzoihzp7mdr4-SaKJadvD6v+eJWbzkQth2-Rg@mail.gmail.com>
 <BF9C0B0F-44FD-4377-BF63-D7ABC6B0FDB3@jakobs.com>
 <CALfOM6KYD+Jc9eRdi18MU0yUpBBS5CgBvYjNJayz07+MBN0fcw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CALfOM6KYD+Jc9eRdi18MU0yUpBBS5CgBvYjNJayz07+MBN0fcw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/61c23ed4.1c69fb81.e4f24.27ac%40mx.google.com>
Precedence: bulk

On Mon, Dec 20, 2021 at 12:24:14PM +0530, Daulat wrote:
> It means, there is no use of pgaudit if we already have log_statements
> enabled?

It depends. log_statments, logs *all* statements of the particular type,
so if you want to log whether the DBA do any data changes at all and set
it to "mod", that means, any other data changes (from the application)
will get logged as well.

Maybe you can live with just log_statement = ddl, or you can set
role-specific log_statement = mod,ddl for the DBA roles (this might not
work on a managed Postgres service).

If not, pgaudit allows to log much more fine-grained and targetted audit
events.


Michael