Re: Advice on logging strategy

From: David Steele <david(at)pgmasters(dot)net>
To: Mike Martin <redtux1(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Advice on logging strategy
Date: 2018-10-12 13:33:01
Message-ID: 5017eca2-e579-36bb-4878-725878ceaeac@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)pgmasters(dot)net

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-10-12 13:40:12 Re: RHEL 7 (systemd) reboot
Previous Message Alban Hertroys 2018-10-12 06:37:42 Re: Want to acquire lock on tables where primary of one table is foreign key on othere