Re: [ADMIN] 9.5 new setting "cluster name" and logging - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [ADMIN] 9.5 new setting "cluster name" and logging
Date
Msg-id 27743.1476816473@sss.pgh.pa.us
Whole thread Raw
In response to Re: [ADMIN] 9.5 new setting "cluster name" and logging  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> 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.

Automatic "csv header" at the start of each logfile, perhaps?  And
force a logfile switch if it changes.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [ADMIN] 9.5 new setting "cluster name" and logging
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Indirect indexes