Re: Removing useless \. at the end of copy in pgbench

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Removing useless \. at the end of copy in pgbench
Date: 2018-09-07 13:57:01
Message-ID: 224ddf7a-a9d5-0bcf-d660-e66870881a36@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30/08/2018 08:39, Peter Eisentraut wrote:
> On 29/08/2018 21:48, Andres Freund wrote:
>> I'd vote for not adding it. It seems almost guaranteed to get out of
>> date without anybody noticing so. Maybe that's overly pragmatic, but I
>> really can't see the harm of not documenting which precise ancient
>> version pgbench doesn't support anymore...
>
> Yeah, chances are that someone is going to make a change that will
> require for example 8.4, and nobody would update this because the
> differences between 8.2 and 8.4 are long forgotten.

It seems there is more enthusiasm on the side of not documenting it, so
I'll close this commit fest entry.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-09-07 14:19:06 Re: pgsql: Refactor dlopen() support
Previous Message Peter Eisentraut 2018-09-07 13:45:10 Re: libpq stricter integer parsing