From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | David Arnold <dar(at)xoe(dot)solutions>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Proposal: Adding json logging |
Date: | 2018-04-16 23:52:58 |
Message-ID: | fbfcebf5-9b7b-db84-b85e-ce1cd1a15c11@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/13/18 20:00, David Arnold wrote:
> I have reviewed some log samples and all DO contain some kind of multi
> line logs which are very uncomfortable to parse reliably in a log streamer.
>
> I asked Michael Paquier about his
> solution: https://github.com/michaelpq/pg_plugins/tree/master/jsonlog
> He was suggestion to take action and propose this extension again to be
> included in contrib:
> https://github.com/michaelpq/pg_plugins/issues/24
I have used https://github.com/mpihlak/pg_logforward in the past, which
seems to be about the same thing.
I have also had good success using syslog. While syslog is not very
structured, the setting syslog_split_messages allows sending log entries
that include newlines in one piece, which works well if you have some
kind of full-text search engine at the receiving end.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2018-04-17 00:11:34 | Re: [HACKERS] Runtime Partition Pruning |
Previous Message | David Rowley | 2018-04-16 21:36:14 | Re: Instability in partition_prune test? |