Re: Add jsonlog log_destination for JSON server logs

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: Andres Freund <andres@anarazel.de>, Sehrope Sarkuni <sehrope@jackdb.com>, Pg Hackers <pgsql-hackers@postgresql.org>, david@fetter.org

Date: 2022-01-07T06:49:47Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Introduce log_destination=jsonlog
- dc686681e079 15.0 landed
Refactor set of routines specific to elog.c
- ac7c80758a7a 15.0 landed
Fix compilation warning in syslogger.c
- 05c4248ad1bf 15.0 landed
Refactor per-destination file rotation in logging collector
- 5c6e33f07153 15.0 landed
Refactor output file handling when forking syslogger under EXEC_BACKEND
- 5b0b699f748e 15.0 landed
Add regression tests for csvlog with the logging collector
- 72b76f76161c 15.0 landed
Refactor the syslogger pipe protocol to use a bitmask for its options
- 2d77d835403a 15.0 landed

On Thu, Jan 06, 2022 at 06:28:26PM -0500, Andrew Dunstan wrote:
> I have tested on an msys2 setup with your v8 patches and I am getting this:
> 
> #   Failed test 'current_logfiles is sane'
> #   at t/004_logrotate.pl line 96.
> #                   'stderr log/postgresql-2022-01-06_222419.log
> # csvlog log/postgresql-2022-01-06_222419.csv

Yes, I was waiting for the latest results, but that did not help at
all.  Something is wrong with the patch, I am not sure what yet, but
that seems like a mistake in the backend part of it rather than the
tests.  I have switched the CF entry as waiting on author until this
is addressed.
--
Michael