Re: [PATCH] Log CSV by default

From: David Fetter <david(at)fetter(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Arkhena <Arkhena(at)gmail(dot)com>, andres(at)anarazel(dot)de, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Log CSV by default
Date: 2018-12-02 17:44:57
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On Sun, Dec 02, 2018 at 12:09:57PM -0500, Tom Lane wrote:
> Arkhena <Arkhena(at)gmail(dot)com> writes:
> > As a consultant with so many customers that simply install Postgres "out of
> > the box", I think that changing log_destination to 'csvlog' and
> > logging_collector to 'on' needs changing at least log_truncate_on_rotation
> > (but certainly also log_filename and log_rotation_age) if we don't want my
> > customers to run out of space sooner or later.
> Yeah, that's another issue that we'd have to confront if we turn
> logging_collector on by default: the default settings for log
> rotation aren't exactly foolproof, and we'd need to make them so.
> (Now having said that, the default setup *without* logging_collector
> isn't exactly foolproof either, since wherever you send stderr to
> will grow without bound. But maybe people are used to dealing with
> that.)
> Independently of changing logging_collector's default, perhaps we could
> agree on changes to the rotation-related defaults so that it's less
> risky to just turn logging_collector on without other changes?

Would rotating daily and keeping a week's worth be reasonable as
defaults? If not, what do you have in mind?

David Fetter <david(at)fetter(dot)org>
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres:

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergei Agalakov 2018-12-02 18:42:20 Re: {PROPOSAL] add session information column to pg_stat_statements
Previous Message didier 2018-12-02 17:39:56 Re: [proposal] Add an option for returning SQLSTATE in psql error message