Re: [PATCH] Log CSV by default

Поиск
Список
Период
Сортировка
От Isaac Morland
Тема Re: [PATCH] Log CSV by default
Дата
Msg-id CAMsGm5cwhGMz8x8PUR5GawJVCxL+Vc__cXZXKd90Nw9pq-GkaQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] Log CSV by default  (Andres Freund <andres@anarazel.de>)
Список 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 по дате отправления:

Предыдущее
От: Chengchao Yu
Дата:
Сообщение: [PATCH] Fix Proposal - Deadlock Issue in Single User Mode When IOFailure Occurs
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: pg_dumpall --exclude-database option