Re: Proposal: More structured logging

From: Sehrope Sarkuni <sehrope(at)jackdb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: Proposal: More structured logging
Date: 2021-08-31 14:46:30
Message-ID: CAH7T-apt6PKWfs0FJNgZKFRNct=e8khdsAjLrH9MB+SW4dU4QA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 24, 2021 at 7:22 PM Michael Paquier <michael(at)paquier(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Denis Hirn 2021-08-31 14:48:30 Re: [PATCH] Allow multiple recursive self-references
Previous Message Daniel Gustafsson 2021-08-31 14:35:30 Re: psql: \dl+ to list large objects privileges