Re: Advice on logging strategy - Mailing list pgsql-general

From David Steele
Subject Re: Advice on logging strategy
Date
Msg-id 5017eca2-e579-36bb-4878-725878ceaeac@pgmasters.net
Whole thread Raw
In response to Advice on logging strategy  (Mike Martin <redtux1@gmail.com>)
Responses Re: Advice on logging strategy  (Mike Martin <redtux1@gmail.com>)
List pgsql-general
On 10/11/18 11:26 AM, Mike Martin wrote:
> 
> This results in enormous log files which take ages to import using copy 
> becuase each execute statement is logged with the parameters chosen
> 
> Is there any way around this?
> 
> I cant find any way to filter dml statements

pgAudit (https://github.com/pgaudit/pgaudit) gives you fine-grain 
control over what is logged by command type, table, or user as well as a 
lot more detail.

-- 
-David
david@pgmasters.net


pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: Want to acquire lock on tables where primary of one table isforeign key on othere
Next
From: Adrian Klaver
Date:
Subject: Re: RHEL 7 (systemd) reboot