Re: Change the csv log to 'key:value' to facilitate the user to understanding and processing of logs

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Jan Wieck <jan(at)wi3ck(dot)info>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Change the csv log to 'key:value' to facilitate the user to understanding and processing of logs
Date: 2022-04-07 05:40:55
Message-ID: Yk55ZziHXJZVHZ8P@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 15, 2022 at 10:33:42AM -0400, Jan Wieck wrote:
> Also, the CSV format, while human readable to a degree, wasn't meant for
> direct, human consumption. It was meant to be read by programs and at the
> time, CSV made the most sense.

FWIW, I have noticed that this patch was still listed in the next CF,
with a reference to an incorrect thread:
https://commitfest.postgresql.org/38/3591/

I have updated the CF entry to poin to this thread, and it is clear
that csvlog is not going to change now so this patch status has been
switched to rejected.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-04-07 05:43:39 Re: pg_dump new feature: exporting functions only. Bad or good idea ?
Previous Message Michael Paquier 2022-04-07 05:36:35 Re: suboverflowed subtransactions concurrency performance optimize