Re: Proposal: Adding json logging - Mailing list pgsql-hackers

From Jordan Deitch
Subject Re: Proposal: Adding json logging
Date
Msg-id 1523806022.996087.1338621800.4958EAA9@webmail.messagingengine.com
Whole thread Raw
In response to Re: Proposal: Adding json logging  (David Arnold <dar@xoe.solutions>)
Responses Re: Proposal: Adding json logging  (Dave Cramer <pg@fastcrypt.com>)
Re: Proposal: Adding json logging  (David Arnold <dar@xoe.solutions>)
List 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
andmore sophisticated over time, I see flat logging becoming more unwieldy. With tools like jq, reading and querying
jsonon the command line is simple and user friendly, and using json for logging capture and aggregation is widely
supportingand embraced.
 


pgsql-hackers by date:

Previous
From: David Arnold
Date:
Subject: Re: Proposal: Adding json logging
Next
From: Dave Cramer
Date:
Subject: Re: Proposal: Adding json logging