pgaudit_analyze process filling up audit log file

From: Dylan Luong <Dylan(dot)Luong(at)unisa(dot)edu(dot)au>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: pgaudit_analyze process filling up audit log file
Date: 2016-12-22 05:29:42
Message-ID: c27d2943a35a47ab928c7b39ba6824e0@ITUPW-EXMBOX2B.UniNet.unisa.edu.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi
I have installed and configured pgAudit extension and the pgAudit Analyzer
https://github.com/pgaudit/pgaudit/tree/REL9_5_STABLE
https://github.com/pgaudit/pgaudit_analyze

I have several databases in the PostgreSQL instance and created the extension and setup the pgaudit analyzer for these database, including the postgres database.

After starting the pgAudit Analyze as a daemon process, ./pgaudit_analyze --daemon /pg_logs/data/pg_log
the log file and the csv file are filling up very fast (1mb per sec) continuously.
The files are filling up with the following continuously:
2016-12-22 15:47:36 ACDT [12735]: [146339-1] db=postgres,user=postgres app=[unknown],host=[local] LOG: duration: 0.106 ms
2016-12-22 15:47:36 ACDT [12735]: [146340-1] db=postgres,user=postgres app=[unknown],host=[local] LOG: duration: 0.021 ms
2016-12-22 15:47:36 ACDT [12735]: [146341-1] db=postgres,user=postgres app=[unknown],host=[local] LOG: duration: 0.086 ms
2016-12-22 15:47:36 ACDT [12735]: [146342-1] db=postgres,user=postgres app=[unknown],host=[local] LOG: duration: 0.022 ms
2016-12-22 15:47:36 ACDT [12735]: [146343-1] db=postgres,user=postgres app=[unknown],host=[local] LOG: duration: 0.167 ms
2016-12-22 15:47:36 ACDT [12735]: [146344-1] db=postgres,user=postgres app=[unknown],host=[local] LOG: duration: 0.030 ms

It only stops when I kill -9 the pgaudit_analyze process.
What is causing this?

Regards
Dylan

Browse pgsql-general by date

  From Date Subject
Next Message Tom DalPozzo 2016-12-22 07:09:52 Re: error updating a tuple after promoting a standby
Previous Message Adrian Klaver 2016-12-22 03:25:14 Re: Too long startup time after each crash.