Re: Separate log for a specfic database - Mailing list pgsql-admin

From Ibrahim Edib Kokdemir
Subject Re: Separate log for a specfic database
Date
Msg-id CABnTomLfVqwvhr9VHyb1yeL7knd-ivXX6jm3MQVQ8Rx5pr6K1A@mail.gmail.com
Whole thread Raw
In response to Re: Separate log for a specfic database  (Keith <keith@keithf4.com>)
List pgsql-admin

We have huge amount of logs files and when using syslog all logs go to journal and journal cannot handle that amount logs. Then we have found nxlog. It is a good solution and double work. Send pg logs as usual and read the read from the file, filter them and either put them into separate files or to another syslog server. Here is the link. Best ever log collector. 

2018-02-28 21:41 GMT+03:00 Keith <keith@keithf4.com>:


On Wed, Feb 28, 2018 at 12:35 PM, Ertan Küçükoğlu <ertan.kucukoglu@1nar.com.tr> wrote:
Hello,

I am using PostgreSQL 9.6.6 on Debian 9 Stretch system. Installed using
apt-get.
I wonder if I can have two log files. One for complete database server and
another for one specific database in the server.
I have already read below link, but cannot understand if that is possible,
or how.
https://www.postgresql.org/docs/9.6/static/runtime-config-logging.html

I appreciate any help.

Regards,
Ertan Küçükoğlu





Not sure what you're reasoning may be, but if it's just to be able to do log analysis, there are tools that can do that for you as long as you have the database name in the log_line_prefix. Take a look at pgbadger

http://dalibo.github.io/pgbadger/

pgsql-admin by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Reliable WAL file shipping over unreliable network
Next
From: Rui DeSousa
Date:
Subject: Re: Reliable WAL file shipping over unreliable network