Re: Proposal: Adding json logging

From: Jordan Deitch <jd(at)rsa(dot)pub>
To: David Arnold <dar(at)xoe(dot)solutions>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Proposal: Adding json logging
Date: 2018-04-15 15:27:02
Message-ID: 1523806022.996087.1338621800.4958EAA9@webmail.messagingengine.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > I would suggest that the community consider whether postgres will log
> multidimensional data. That will weigh into the decision of json vs.
> another format quite significantly. I am a fan of the json5 spec (
> https://json5.org/), though adoption of this is quite poor.
>
> What do you mean by multidimensional data? Arrays/maps?
>
> I think there is no advantage of multidimensional vs prefixed flat logging
> unless data structure gets really nastily nested.
>
> What case where you thinking of?

Exactly - arrays, maps, nested json objects. It's more organized and easier to reason about. As postgresql becomes more and more sophisticated over time, I see flat logging becoming more unwieldy. With tools like jq, reading and querying json on the command line is simple and user friendly, and using json for logging capture and aggregation is widely supporting and embraced.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2018-04-15 15:29:18 Re: Proposal: Adding json logging
Previous Message David Arnold 2018-04-15 15:04:17 Re: Proposal: Adding json logging