From: | David Arnold <dar(at)xoe(dot)solutions> |
---|---|
To: | Jordan Deitch <jd(at)rsa(dot)pub> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Proposal: Adding json logging |
Date: | 2018-04-15 15:04:17 |
Message-ID: | CAH6vsWLTu6VXnZv+ASAvwLgkvvLzFY0XOmqR9CQ7iKuE2K9ngg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>A slightly larger lift would include escaping newlines and ensuring that JSON
output is always single lines, however long.
I think that's necessary, actually I was implicitly assuming that as a
prerequisite. I cannot imagine anything else beeing actually useful.
Alternatively, I'm sure logfmt has a well thought-through solution for that
:-)
> 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?
El sáb., 14 abr. 2018, 6:25 p.m., Jordan Deitch <jd(at)rsa(dot)pub> escribió:
> 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.
>
>
> ---
> Jordan Deitch
> https://id.rsa.pub
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jordan Deitch | 2018-04-15 15:27:02 | Re: Proposal: Adding json logging |
Previous Message | Magnus Hagander | 2018-04-15 12:15:42 | Re: Online enabling of checksums |