Re: BUG #15228: pgbench custom script numbering off-by-one

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: steven(dot)winfield(at)cantabcapital(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15228: pgbench custom script numbering off-by-one
Date: 2018-06-04 20:00:35
Message-ID: 6240.1528142435@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> There's an off-by-one error in script numbering in the human readable vs.
> machine readable logs, i.e.:
> ...
> In the human readable output the scripts are numbered 1 and 2:
> ...
> ...but in the 4th column of the log files written by pgbench they are
> numbered 0 and 1:

Hmm, yeah, it's inconsistent, but I wonder whether it's worth the pain
to fix. I'd be quite hesitant to change the log output because that'd
likely break peoples' analysis scripts. So possibly we could resolve
it by using 0-based numbering in the human-readable output, but that
would confuse things too perhaps.

Maybe we should just document it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2018-06-04 23:06:02 Re: BUG #15225: [XX000] ERROR: invalid DSA memory alloc request size 1073741824 / Where: parallel worker
Previous Message Tom Lane 2018-06-04 19:56:36 Re: BUG #15229: Crash when using PQgetvalue