Re: BUG #15228: pgbench custom script numbering off-by-one - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15228: pgbench custom script numbering off-by-one
Date
Msg-id 6240.1528142435@sss.pgh.pa.us
Whole thread Raw
In response to BUG #15228: pgbench custom script numbering off-by-one  (PG Bug reporting form <noreply@postgresql.org>)
Responses RE: BUG #15228: pgbench custom script numbering off-by-one  (Steven Winfield <Steven.Winfield@cantabcapital.com>)
List pgsql-bugs
=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.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


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15229: Crash when using PQgetvalue
Next
From: Thomas Munro
Date:
Subject: Re: BUG #15225: [XX000] ERROR: invalid DSA memory alloc request size1073741824 / Where: parallel worker