| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | David Arnold <dar(at)xoe(dot)solutions>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Proposal: Adding json logging |
| Date: | 2018-04-17 11:16:27 |
| Message-ID: | f57b0c8c-c4e3-a2fc-de02-45027d4fbc39@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/16/18 23:12, Michael Paquier wrote:
>> 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.
> syslog suffers from the possibility to lose messages if I recall
> correctly, right? This may matter for some critical environments.
Depends on whether you configure it to use TCP or UDP.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2018-04-17 11:55:21 | Re: Proposal: Adding json logging |
| Previous Message | Euler Taveira | 2018-04-17 11:07:29 | Re: pg_recvlogical broken in back branches |