Re: Proposal: Adding json logging

> Plus it's likely only a short-lived interchange format, not something to be
retained for a long period.

Absolutely.

There might be an argument that it's not easy on the eyes in the case it
would be consumed by a pair of them. It's absolutely valid. Golang
community has found a solution for that called logfmt, which I personally
appreciate.

It's somewhat similar to JSON, but a lot easier on the eyes, so if logs go
to the stdout of a docker container and are forwarded afterwards, you still
can attach to the live container logs and actually understand something.

If it's for that reason, logfmt is possibly preferable and there is already
a lot of standard tooling available for it.

Any thoughts on that argument?

Best Regards

El sáb., 14 abr. 2018, 7:59 a.m., Craig Ringer <craig(at)2ndquadrant(dot)com>
escribió:

> On 14 April 2018 at 11:24, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> > "I proposed that a couple of years back, to be rejected as the key names
> > are too much repetitive and take too much place.
>
> gzip is astonishingly good at dealing with that, so I think that's
> actually a bit of a silly reason to block it.
>
> Plus it's likely only a short-lived interchange format, not something
> to be retained for a long period.
>
> --
> Craig Ringer http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>