Re: Proposal: More structured logging - Mailing list pgsql-hackers

From Sehrope Sarkuni
Subject Re: Proposal: More structured logging
Date
Msg-id CAH7T-apt6PKWfs0FJNgZKFRNct=e8khdsAjLrH9MB+SW4dU4QA@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: More structured logging  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Proposal: More structured logging  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Aug 24, 2021 at 7:22 PM Michael Paquier <michael@paquier.xyz> wrote:
From a code perspective, and while on it, we could split a bit elog.c
and move the log entries generated for each format into their own
file.  That would be cleaner for CSV and JSON.  As a whole I don't
have an objection with moving the JSON format into core.  If one
proposes a patch, feel free to reuse the code from the module I have
released.

I had a patch that does exactly this from a few years ago. It started off copying a bunch out of your json logging module and adds it as a new "jsonlog" destination.

It needed some cleanup due to bit rot, but it now builds and works atop master. I'll post it in its own thread.

Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/

 

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: psql: \dl+ to list large objects privileges
Next
From: Denis Hirn
Date:
Subject: Re: [PATCH] Allow multiple recursive self-references