Re: pgsql: Improve scripting language in pgbench

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Improve scripting language in pgbench
Date: 2018-01-23 17:32:11
Message-ID: 12473163-6aa3-52df-8efd-29497d32c285@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 1/10/18 07:36, Fabien COELHO wrote:
> I just noticed while rebasing stuff that there is some crust in
> "pgbench/t/001_pgbench_with_server.pl" coming from this patch:
>
> +=head
> +
> +} });
> +
> +=cut
>
> I cannot find any use for these lines which are ignored by perl execution
> anyway. It may be some leftovers from debugging which got past everyone.
> If so, I think that it is better removed, see the attached cleanup patch.

fixed

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-01-23 17:42:14 pgsql: Documentation fix: pg_ctl no longer makes connection attempts.
Previous Message Peter Eisentraut 2018-01-23 17:31:30 pgsql: pgbench: Remove accidental garbage in test file

Browse pgsql-hackers by date

  From Date Subject
Next Message Marco Nenciarini 2018-01-23 17:47:16 Re: [PATCH] Logical decoding of TRUNCATE
Previous Message Petr Jelinek 2018-01-23 17:25:05 Re: [PATCH] Logical decoding of TRUNCATE