From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Stephen Frost <sfrost@snowman.net>,
        Thomas Munro <thomas.munro@enterprisedb.com>,
        Andres Freund <andres@anarazel.de>, Evan Rempel <erempel@uvic.ca>,
        "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>,
        Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [ADMIN] 9.5 new setting "cluster name" and logging
In-reply-to: 
 <CA+TgmoaAJMZ6kuapWbWPorz0wk5BqdTqWSkwD=_T1UZB3hYfEQ@mail.gmail.com>
References: <1377186808.57546.YahooMailNeo@web193505.mail.sg3.yahoo.com>
 <A737B7A37273E048B164557ADEF4A58B17C08086@ntex2010a.host.magwien.gv.at>
 <1377494614.9111.YahooMailNeo@web193506.mail.sg3.yahoo.com>
 <A737B7A37273E048B164557ADEF4A58B17C0876C@ntex2010a.host.magwien.gv.at>
 <56AC5601.5040208@uvic.ca>
 <20160208142429.5by57csmc75gorg7@alap3.anarazel.de>
 <CAEepm=3qzm=iROikNJFdjyZD3AJPEr3m_RFcmazBjZrzAVNoHw@mail.gmail.com>
 <20161017222405.GA13284@tamriel.snowman.net>
 <CA+TgmoaAJMZ6kuapWbWPorz0wk5BqdTqWSkwD=_T1UZB3hYfEQ@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Tue, 18 Oct 2016 14:25:27 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <27742.1476816473.1@sss.pgh.pa.us>
Date: Tue, 18 Oct 2016 14:47:53 -0400
Message-ID: <27743.1476816473@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers