Re: [HACKERS] 9.5 new setting "cluster name" and logging

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] 9.5 new setting "cluster name" and logging
Дата
Msg-id CA+TgmoaAJMZ6kuapWbWPorz0wk5BqdTqWSkwD=_T1UZB3hYfEQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] 9.5 new setting "cluster name" and logging  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: [HACKERS] 9.5 new setting "cluster name" and logging  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: [HACKERS] 9.5 new setting "cluster name" and logging  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-admin
On Mon, Oct 17, 2016 at 6:24 PM, Stephen Frost <sfrost@snowman.net> wrote:
> I'm with Thomas on this and I disagree that the "csvlog bloat" argument
> has merit.  If we're worried about bloat in csv then we should provide a
> way for users to control what goes into the csvlog, not argue that
> something which is clearly useful be excluded.

I agree, but I think if we do that it would be highly desirable do
something to make the format discoverable.  For example, at the
beginning of each file and whenever the format changes, we write some
kind of unmistakable header line into the file identifying what fields
will be present on each line thereafter.  It's undesirable for log
analysis tools to need to contain logic that tries (imperfectly, no
doubt) to reverse-engineer the field list.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-admin по дате отправления:

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: [HACKERS] 9.5 new setting "cluster name" and logging
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] 9.5 new setting "cluster name" and logging