| From: | Mike Martin <redtux1(at)gmail(dot)com> |
|---|---|
| To: | david(at)pgmasters(dot)net |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Advice on logging strategy |
| Date: | 2018-10-12 14:17:08 |
| Message-ID: | CAOwYNKajjAvJ=MvJm5dDcKrLhiXMYTg8QYjo5hX=w8tFMbFZ4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks!
On Fri, 12 Oct 2018 at 14:33, David Steele <david(at)pgmasters(dot)net> wrote:
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2018-10-12 14:50:59 | Re: Compile psql 9.6 with SSL Version 1.1.0 |
| Previous Message | Ádám Maracska | 2018-10-12 14:15:59 | Compile psql 9.6 with SSL Version 1.1.0 |