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

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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-08-29 17:45:44
Message-ID: alpine.DEB.2.21.1808291942330.14012@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> The "may" is because I could *not* test:
>
> Works for me with 8.2.

Thanks for the confirmation.

> Earlier branches fail immediately: dropping old tables... ERROR:
> syntax error at or near "exists" LINE 1: drop table if exists
> pgbench_accounts, pgbench_branches, pgb...
> ^

Ok, even before the create table with a fillfactor.

> We could probably fix that if anyone cared, but I doubt anyone does.

Indeed, if people needed using a new pgbench against a that old server,
they would have complained.

The point was just to document the current status of pgbench
compatibility, and 8.2 onward is the answer.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-08-29 18:00:12 Re: buildfarm: could not read block 3 in file "base/16384/2662": read only 0 of 8192 bytes
Previous Message Robert Haas 2018-08-29 17:38:57 Re: FailedAssertion on partprune