Michael Paquier <michael.paquier@gmail.com> writes:
> Now what about a json format logging with one json object per log entry?
> A single json entry would need more space than a csv one as we need to
> track the field names with their values. Also, there is always the
> argument that if an application needs json-format logs, it could use
> csvlog on Postgres-side and do the transformation itself. But wouldn't
> it be a win for application or tools if such an option is available
> in-core?
I think the extra representational overhead is already a good reason to
say "no". There is not any production scenario I've ever heard of where
log output volume isn't a consideration.
regards, tom lane
