Re: Add jsonlog log_destination for JSON server logs

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, david(at)fetter(dot)org
Subject: Re: Add jsonlog log_destination for JSON server logs
Date: 2022-01-07 06:49:47
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

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/ 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.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-01-07 07:11:58 Re: fix libpq comment
Previous Message Michael Paquier 2022-01-07 06:43:06 Re: Refactoring of compression options in pg_basebackup