Re: Add jsonlog log_destination for JSON server logs

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Sehrope Sarkuni <sehrope(at)jackdb(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, david(at)fetter(dot)org
Subject: Re: Add jsonlog log_destination for JSON server logs
Date: 2021-10-08 03:28:58
Message-ID: YV+6+ur5kG/
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Oct 05, 2021 at 04:18:17PM +0900, Michael Paquier wrote:
> 0002 and 0004 could be more polished and most of their pieces had
> better be squashed together. 0003, though, would improve the case of
> WIN32 where only csvlog is enabled so as log entries are properly
> redirected to the event logs if the redirection is not done yet. I'd
> like to move on with 0001 and 0003 as independent pieces.

0001 and 0003 have been applied independently, attached is a rebased

Attachment Content-Type Size
v5-0001-Some-refactoring-of-elog-specific-routines.patch text/x-diff 8.7 KB
v5-0002-Refactor-CSV-specific-code-into-its-own-file.patch text/x-diff 17.0 KB
v5-0003-JSON-logging.patch text/x-diff 29.4 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2021-10-08 03:29:42 Re: pg_dump does not dump tables created in information_schema schema
Previous Message 2021-10-08 03:07:00 RE: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns