Re: Proposal: Adding json logging

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: Jordan Deitch <jd(at)rsa(dot)pub>
Cc: David Arnold <dar(at)xoe(dot)solutions>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Proposal: Adding json logging
Date: 2018-04-15 15:29:18
Message-ID: CADK3HH+9jnRm9DF8q+DFMHkki_qY03cVBRbx5qPcBXJ6n3nA1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15 April 2018 at 11:27, Jordan Deitch <jd(at)rsa(dot)pub> wrote:

> > > 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.
>

Exactly what are you logging here ??? Why would I need to see a
multi-dimensional array in the log ?

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jordan Deitch 2018-04-15 15:46:58 Re: Proposal: Adding json logging
Previous Message Jordan Deitch 2018-04-15 15:27:02 Re: Proposal: Adding json logging