From: | "Paul van Rixel" <p(dot)van(dot)rixel(at)trendpage(dot)nl> |
---|---|
To: | <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | split postgresql logfile |
Date: | 2021-11-29 11:12:11 |
Message-ID: | 022401d7e511$f9135f00$eb3a1d00$@van.rixel@trendpage.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi all,
I wondered if it is worthwile to split the general postgresql.log file into
a logfile for rdbms related log entries and a connection based logfile?
Just like the Oracle rdbms.log and the listener.log for connections.
Now the postgresql.logs are polluted with log connections/disconnection,
Agent monitoring entries and in between some entries which need some
attention but you missed them. I know the option exists to disable
log_(dis)connections but because of auditing this option must be enabled.
We don't use a tool like Grafana yet and with pgBadger we are experimenting
but skipping "unnessary" lines makes the manually reading of the logs much
more clear.
Any hints, tips or best practice scenario is welcome!
Thanks and have a nice day,
Best regards,
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Dirk Krautschick | 2021-11-29 12:04:20 | Experience with node-pg-migrate |
Previous Message | Dischner, Anton | 2021-11-29 10:10:57 | AW: What do you do with a long running rollback |