Re: [PATCH] Log CSV by default

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Log CSV by default
Date: 2018-11-30 23:11:03
Message-ID: 20181130231103.GJ3415@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greetings,

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2018-11-30 19:53:18 +0100, David Fetter wrote:
> >> This makes it much simpler for computers to use the logs while not
> >> making it excessively difficult for humans to use them.
>
> > While perhaps not excessively so, I think it increases the difficulty
> > sufficiently that I'm against such a proposal.
>
> I don't like this either. People who prefer CSV format can select it
> trivially. Those who don't are going to be annoyed at us for changing
> behavior that's stood for many years.

Agreed. Frankly, even if we made this the default, I doubt packagers
would decide to go with it because of the issues raised here.

> I think we should reject this out of hand.

Agreed.

Thanks!

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2018-11-30 23:16:01 Re: Reviving the "Stopping logical replication protocol" patch from Vladimir Gordichuk
Previous Message Michael Paquier 2018-11-30 23:08:04 Re: pgsql: Avoid duplicate XIDs at recovery when building initial snapshot