Re: Removing useless \. at the end of copy in pgbench - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Removing useless \. at the end of copy in pgbench
Date
Msg-id 20180829194813.xus76xna3z7qjodj@alap3.anarazel.de
Whole thread Raw
In response to Re: Removing useless \. at the end of copy in pgbench  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: Removing useless \. at the end of copy in pgbench
List pgsql-hackers
On 2018-08-29 21:42:42 +0200, Fabien COELHO wrote:
> 
> Hello,
> 
> > What about:
> > 
> > """
> > Pgbench requires a PostgreSQL version 8.2 or above server.
> > """
> > 
> > Some information is provided...
> > 
> > I understood that Tom found that an explicit compatibility note would be
> > welcome, so I provided one. I'm also fine with saying nothing.
> 
> Here is a patch with the following accurate information:
> 
> """
> In order to run, pgbench requires a PostgreSQL server version 8.2 or above.
> """
> 
> 8.2 has been tested by Tom, and is required because of DROP TABLE IF EXISTS
> & CREATE TABLE ... FILLFACTOR, which I pointed out in a mail upthread.
> 
> Now if the information is not added to the doc, this is also fine with me.

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...

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes
Next
From: Andres Freund
Date:
Subject: Re: buildfarm: could not read block 3 in file "base/16384/2662":read only 0 of 8192 bytes