Home Explore Blog CI



postgresql

11th chunk of `doc/src/sgml/ref/pgbench.sgml`
921cd2ac921c7155a8a78d24229e982735bfd3ef005c60f80000000100000fa7
 <term><option>-v</option></term>
      <term><option>--vacuum-all</option></term>
      <listitem>
       <para>
        Vacuum all four standard tables before running the test.
        With neither <option>-n</option> nor <option>-v</option>, <application>pgbench</application> will vacuum the
        <structname>pgbench_tellers</structname> and <structname>pgbench_branches</structname>
        tables, and will truncate <structname>pgbench_history</structname>.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="pgbench-option-aggregate-interval">
      <term><option>--aggregate-interval=<replaceable>seconds</replaceable></option></term>
      <listitem>
       <para>
        Length of aggregation interval (in seconds).  May be used only
        with <option>-l</option> option.  With this option, the log contains
        per-interval summary data, as described below.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="pgbench-option-exit-on-abort">
      <term><option>--exit-on-abort</option></term>
      <listitem>
       <para>
        Exit immediately when any client is aborted due to some error. Without
        this option, even when a client is aborted, other clients could
        continue their run as specified by <option>-t</option>
        or <option>-T</option> option, and <application>pgbench</application>
        will print an incomplete results in this case.
       </para>
       <para>
        Note that serialization failures or deadlock failures do not abort the
        client, so they are not affected by this option.
        See <xref linkend="failures-and-retries"/> for more information.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="pgbench-option-failures-detailed">
      <term><option>--failures-detailed</option></term>
      <listitem>
       <para>
        Report failures in per-transaction and aggregation logs, as well as in
        the main and per-script reports, grouped by the following types:
        <itemizedlist>
         <listitem>
          <para>serialization failures;</para>
         </listitem>
         <listitem>
          <para>deadlock failures;</para>
         </listitem>
        </itemizedlist>
        See <xref linkend="failures-and-retries"/> for more information.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="pgbench-option-log-prefix">
      <term><option>--log-prefix=<replaceable>prefix</replaceable></option></term>
      <listitem>
       <para>
        Set the filename prefix for the log files created by
        <option>--log</option>.  The default is <literal>pgbench_log</literal>.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="pgbench-option-max-tries">
      <term><option>--max-tries=<replaceable>number_of_tries</replaceable></option></term>
      <listitem>
       <para>
        Enable retries for transactions with serialization/deadlock errors and
        set the maximum number of these tries. This option can be combined with
        the <option>--latency-limit</option> option which limits the total time
        of all transaction tries; moreover, you cannot use an unlimited number
        of tries (<literal>--max-tries=0</literal>) without
        <option>--latency-limit</option> or <option>--time</option>.
        The default value is 1 and transactions with serialization/deadlock
        errors are not retried. See <xref linkend="failures-and-retries"/>
        for more information about retrying such transactions.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="pgbench-option-progress-timestamp">
      <term><option>--progress-timestamp</option></term>
      <listitem>
       <para>
        When showing progress (option <option>-P</option>), use a timestamp
        (Unix epoch) instead of the number of seconds since the
        beginning of the run.  The unit is in seconds, with millisecond
        precision

Title: pgbench Options: Vacuum All, Aggregate Interval, Exit on Abort, Detailed Failures, Log Prefix, Max Tries, and Progress Timestamp
Summary
This section describes pgbench options for vacuuming tables before a test, setting the log aggregation interval, exiting on client abort, reporting detailed failure types, setting the log filename prefix, enabling transaction retries after serialization/deadlock errors, and displaying a timestamp for progress reports.