On Mon, Dec 03, 2018 at 07:18:31PM +0100, Gilles Darold wrote:
> Le 30/11/2018 à 19:53, David Fetter a écrit :
> > This makes it much simpler for computers to use the logs while not
> > making it excessively difficult for humans to use them.
>
> I'm also not very comfortable with this change. For a pgBadger point
> of view I don't know an existing library to parse csv log in
> multi-process mode. The only way I know is to split the file or load
> chunks in memory which is not really recommended with huge log
> files. I am not saying that this is not possible to have a Perl CSV
> library allowing multi-process but this require some additional days
> of work.
How about other structured log formats? Would one for JSON work
better?
> Also at this time I have not received any feature request for that,
> maybe the use of csvlog format is not so common.
Part of the reason it's uncommon is that it's not the default we ship
with, and defaults influence this very much.
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
