Re: pgbench - minor doc improvements

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench - minor doc improvements
Date: 2016-07-11 04:51:03
Message-ID: CAB7nPqQZxwxpEGAuq8X17VPi+9VYMGFoqd8t6yJcxz9yru3aGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 9, 2016 at 4:48 PM, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>
> Minor pgbench documentation improvements so that the description is more
> precise:
>
> - a pgbench script may not contain SQL commands, it only needs not to be
> empty.

Halfly true as far as I recall. This works and generates two queries:
SELECT 1; \set two 3
SELECT :two;
But any query added after the meta-command cannot be parsed.

> - point out explicitely variable setting meta commands.
> - the formula is short enough to fit on a line.

<literallayout>
-f(x) = PHI(2.0 * parameter * (x - mu) / (max - min + 1)) /
- (2.0 * PHI(parameter) - 1)
+f(x) = PHI(2.0 * parameter * (x - mu) / (max - min + 1)) / (2.0 *
PHI(parameter) - 1)
At full-length this is 85 characters. But I agree that it is more
readable to put that into a single line. Now we could as well trick
the limit by using "param" instead of "parameter".
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-07-11 04:53:02 Re: Issue with bgworker, SPI and pgstat_report_stat
Previous Message Michael Paquier 2016-07-11 04:41:00 Re: pgbench - minor fix for meta command only scripts