Re: [PATCH] Log CSV by default - Mailing list pgsql-hackers

From Isaac Morland
Subject Re: [PATCH] Log CSV by default
Date
Msg-id CAMsGm5cwhGMz8x8PUR5GawJVCxL+Vc__cXZXKd90Nw9pq-GkaQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Log CSV by default  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers

I think having a bin/pg_logparse tool that can parse postgres' config
file and attempt to parse the log contents in whatever format they are
would be much much more useful. Obviously not every log_line_prefix can
be parsed unambiguously, but a lot of formats can, and a lot more
formats can be made unambiguous (e.g. adding escape logic to application
name logging would be very useful).

Aren't application names set by the client? If they are currently logged without escaping, couldn't a client insert arbitrary binary content such as terminal control sequences into log files, with potentially unpleasant results? Or is there some sort of filter already in place somewhere? Should I investigate?

pgsql-hackers by date:

Previous
From: Chengchao Yu
Date:
Subject: [PATCH] Fix Proposal - Deadlock Issue in Single User Mode When IOFailure Occurs
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_dumpall --exclude-database option