<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="mysqlbinlog">
      </a>
      6.6.9 mysqlbinlog — Utility for Processing Binary Log Files
     </h3>
    </div>
   </div>
  </div>
  <div class="toc">
   <dl class="toc">
    <dt>
     <span class="section">
      <a href="mysqlbinlog-hexdump.html">
       6.6.9.1 mysqlbinlog Hex Dump Format
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="mysqlbinlog-row-events.html">
       6.6.9.2 mysqlbinlog Row Event Display
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="mysqlbinlog-backup.html">
       6.6.9.3 Using mysqlbinlog to Back Up Binary Log Files
      </a>
     </span>
    </dt>
    <dt>
     <span class="section">
      <a href="mysqlbinlog-server-id.html">
       6.6.9.4 Specifying the mysqlbinlog Server ID
      </a>
     </span>
    </dt>
   </dl>
  </div>
  <a class="indexterm" name="idm46045305260944">
  </a>
  <p>
   The server's binary log consists of files containing
   <span class="quote">
    “
    <span class="quote">
     events
    </span>
    ”
   </span>
   that describe modifications to database
        contents. The server writes these files in binary format. To
        display their contents in text format, use the
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   utility. You can also use
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   to display the contents of relay
        log files written by a replica server in a replication setup
        because relay logs have the same format as binary logs. The
        binary log and relay log are discussed further in
   <a class="xref" href="binary-log.html" title="7.4.4 The Binary Log">
    Section 7.4.4, “The Binary Log”
   </a>
   , and
   <a class="xref" href="replica-logs.html" title="19.2.4 Relay Log and Replication Metadata Repositories">
    Section 19.2.4, “Relay Log and Replication Metadata Repositories”
   </a>
   .
  </p>
  <p>
   Invoke
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   like this:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa21232066"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog <span class="token punctuation">[</span><em class="replaceable">options</em><span class="token punctuation">]</span> <em class="replaceable">log_file</em> <span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span></code></pre>
  </div>
  <p>
   For example, to display the contents of the binary log file
        named
   <code class="filename">
    binlog.000003
   </code>
   , use this command:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa19097330"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog binlog<span class="token punctuation">.</span>000003</code></pre>
  </div>
  <p>
   The output includes events contained in
   <code class="filename">
    binlog.000003
   </code>
   . For statement-based logging,
        event information includes the SQL statement, the ID of the
        server on which it was executed, the timestamp when the
        statement was executed, how much time it took, and so forth. For
        row-based logging, the event indicates a row change rather than
        an SQL statement. See
   <a class="xref" href="replication-formats.html" title="19.2.1 Replication Formats">
    Section 19.2.1, “Replication Formats”
   </a>
   , for
        information about logging modes.
  </p>
  <p>
   Events are preceded by header comments that provide additional
        information. For example:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-none"><div class="docs-select-all right" id="sa11419358"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-none"># at 141
#100309  9:28:36 server id 123  end_log_pos 245
  Query thread_id=3350  exec_time=11  error_code=0</code></pre>
  </div>
  <p>
   In the first line, the number following
   <code class="literal">
    at
   </code>
   indicates the file offset, or starting position, of the event in
        the binary log file.
  </p>
  <p>
   The second line starts with a date and time indicating when the
        statement started on the server where the event originated. For
        replication, this timestamp is propagated to replica servers.
   <code class="literal">
    server id
   </code>
   is the
   <a class="link" href="replication-options.html#sysvar_server_id">
    <code class="literal">
     server_id
    </code>
   </a>
   value of the server
        where the event originated.
   <code class="literal">
    end_log_pos
   </code>
   indicates where the next event starts (that is, it is the end
        position of the current event + 1).
   <code class="literal">
    thread_id
   </code>
   indicates which thread executed the event.
   <code class="literal">
    exec_time
   </code>
   is the time spent executing the
        event, on a replication source server. On a replica, it is the
        difference of the end execution time on the replica minus the
        beginning execution time on the source. The difference serves as
        an indicator of how much replication lags behind the source.
   <code class="literal">
    error_code
   </code>
   indicates the result from
        executing the event. Zero means that no error occurred.
  </p>
  <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Note
   </div>
   <p>
    When using event groups, the file offsets of events may be
          grouped together and the comments of events may be grouped
          together. Do not mistake these grouped events for blank file
          offsets.
   </p>
  </div>
  <p>
   The output from
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   can be
        re-executed (for example, by using it as input to
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   ) to redo the statements in the log.
        This is useful for recovery operations after an unexpected
        server exit. For other usage examples, see the discussion later
        in this section and in
   <a class="xref" href="point-in-time-recovery.html" title="9.5 Point-in-Time (Incremental) Recovery">
    Section 9.5, “Point-in-Time (Incremental) Recovery”
   </a>
   .
        To execute the internal-use
   <a class="link" href="binlog.html" title="15.7.8.1 BINLOG Statement">
    <code class="literal">
     BINLOG
    </code>
   </a>
   statements used by
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   , the user requires the
   <a class="link" href="privileges-provided.html#priv_binlog-admin">
    <code class="literal">
     BINLOG_ADMIN
    </code>
   </a>
   privilege (or the
        deprecated
   <a class="link" href="privileges-provided.html#priv_super">
    <code class="literal">
     SUPER
    </code>
   </a>
   privilege), or
        the
   <a class="link" href="privileges-provided.html#priv_replication-applier">
    <code class="literal">
     REPLICATION_APPLIER
    </code>
   </a>
   privilege
        plus the appropriate privileges to execute each log event.
  </p>
  <p>
   You can use
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   to read binary log
        files directly and apply them to the local MySQL server. You can
        also read binary logs from a remote server by using the
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
    <code class="option">
     --read-from-remote-server
    </code>
   </a>
   option. To read remote binary logs, the connection parameter
        options can be given to indicate how to connect to the server.
        These options are
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_host">
    <code class="option">
     --host
    </code>
   </a>
   ,
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_password">
    <code class="option">
     --password
    </code>
   </a>
   ,
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_port">
    <code class="option">
     --port
    </code>
   </a>
   ,
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_protocol">
    <code class="option">
     --protocol
    </code>
   </a>
   ,
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_socket">
    <code class="option">
     --socket
    </code>
   </a>
   , and
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_user">
    <code class="option">
     --user
    </code>
   </a>
   .
  </p>
  <p>
   When binary log files have been encrypted,
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   cannot read them directly, but
        can read them from the server using the
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
    <code class="option">
     --read-from-remote-server
    </code>
   </a>
   option. Binary log files are encrypted when the server's
   <a class="link" href="replication-options-binary-log.html#sysvar_binlog_encryption">
    <code class="literal">
     binlog_encryption
    </code>
   </a>
   system
        variable is set to
   <code class="literal">
    ON
   </code>
   . The
   <a class="link" href="show-binary-logs.html" title="15.7.7.2 SHOW BINARY LOGS Statement">
    <code class="literal">
     SHOW BINARY LOGS
    </code>
   </a>
   statement shows
        whether a particular binary log file is encrypted or
        unencrypted. Encrypted and unencrypted binary log files can also
        be distinguished using the magic number at the start of the file
        header for encrypted log files (
   <code class="literal">
    0xFD62696E
   </code>
   ),
        which differs from that used for unencrypted log files
        (
   <code class="literal">
    0xFE62696E
   </code>
   ). Note that
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   returns a suitable error if you
        attempt to read an encrypted binary log file directly, but older
        versions of
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   do not recognise the
        file as a binary log file at all. For more information on binary
        log encryption, see
   <a class="xref" href="replication-binlog-encryption.html" title="19.3.2 Encrypting Binary Log Files and Relay Log Files">
    Section 19.3.2, “Encrypting Binary Log Files and Relay Log Files”
   </a>
   .
  </p>
  <p>
   When binary log transaction payloads have been compressed,
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   automatically decompresses and
        decodes the transaction payloads, and prints them as it would
        uncompressed events. When
   <a class="link" href="replication-options-binary-log.html#sysvar_binlog_transaction_compression">
    <code class="literal">
     binlog_transaction_compression
    </code>
   </a>
   is set to
   <code class="literal">
    ON
   </code>
   , transaction payloads are
        compressed and then written to the server's binary log file as a
        single event (a
   <code class="literal">
    Transaction_payload_event
   </code>
   ).
        With the
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verbose">
    <code class="option">
     --verbose
    </code>
   </a>
   option,
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   adds comments stating the
        compression algorithm used, the compressed payload size that was
        originally received, and the resulting payload size after
        decompression.
  </p>
  <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Note
   </div>
   <p>
    The end position (
    <code class="literal">
     end_log_pos
    </code>
    ) that
    <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
     <span class="command">
      <strong>
       mysqlbinlog
      </strong>
     </span>
    </a>
    states for an individual event
          that was part of a compressed transaction payload is the same
          as the end position of the original compressed payload.
          Multiple decompressed events can therefore have the same end
          position.
   </p>
   <p>
    <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
     <span class="command">
      <strong>
       mysqlbinlog
      </strong>
     </span>
    </a>
    's own connection compression
          does less if transaction payloads are already compressed, but
          still operates on uncompressed transactions and headers.
   </p>
  </div>
  <p>
   For more information on binary log transaction compression, see
   <a class="xref" href="binary-log-transaction-compression.html" title="7.4.4.5 Binary Log Transaction Compression">
    Section 7.4.4.5, “Binary Log Transaction Compression”
   </a>
   .
  </p>
  <p>
   When running
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   against a large
        binary log, be careful that the filesystem has enough space for
        the resulting files. To configure the directory that
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   uses for temporary files, use the
   <code class="literal">
    TMPDIR
   </code>
   environment variable.
  </p>
  <p>
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   sets the value of
   <a class="link" href="server-system-variables.html#sysvar_pseudo_replica_mode">
    <code class="literal">
     pseudo_replica_mode
    </code>
   </a>
   to true
        before executing any SQL statements. This system variable
        affects the handling of XA transactions, the
   <code class="literal">
    original_commit_timestamp
   </code>
   replication delay
        timestamp and the
   <a class="link" href="replication-options-source.html#sysvar_original_server_version">
    <code class="literal">
     original_server_version
    </code>
   </a>
   system
        variable, and unsupported SQL modes.
  </p>
  <p>
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   supports the following options,
        which can be specified on the command line or in the
   <code class="literal">
    [mysqlbinlog]
   </code>
   and
   <code class="literal">
    [client]
   </code>
   groups of an option file. For information about option files
        used by MySQL programs, see
   <a class="xref" href="option-files.html" title="6.2.2.2 Using Option Files">
    Section 6.2.2.2, “Using Option Files”
   </a>
   .
  </p>
  <div class="table">
   <a name="idm46045305178320">
   </a>
   <p class="title">
    <b>
     Table 6.20 mysqlbinlog Options
    </b>
   </p>
   <div class="table-contents">
    <table frame="box" rules="all" summary="Command-line options available for mysqlbinlog.">
     <colgroup>
      <col style="width: 35%"/>
      <col style="width: 64%"/>
     </colgroup>
     <thead>
      <tr>
       <th>
        Option Name
       </th>
       <th>
        Description
       </th>
      </tr>
     </thead>
     <tbody>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_base64-output">
         --base64-output
        </a>
       </td>
       <td>
        Print binary log entries using base-64 encoding
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_bind-address">
         --bind-address
        </a>
       </td>
       <td>
        Use specified network interface to connect to MySQL Server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_binlog-row-event-max-size">
         --binlog-row-event-max-size
        </a>
       </td>
       <td>
        Binary log max event size
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_character-sets-dir">
         --character-sets-dir
        </a>
       </td>
       <td>
        Directory where character sets are installed
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_compress">
         --compress
        </a>
       </td>
       <td>
        Compress all information sent between client and server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_compression-algorithms">
         --compression-algorithms
        </a>
       </td>
       <td>
        Permitted compression algorithms for connections to server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_connection-server-id">
         --connection-server-id
        </a>
       </td>
       <td>
        Used for testing and debugging. See text for applicable default values and other particulars
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_database">
         --database
        </a>
       </td>
       <td>
        List entries for just this database
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_debug">
         --debug
        </a>
       </td>
       <td>
        Write debugging log
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_debug-check">
         --debug-check
        </a>
       </td>
       <td>
        Print debugging information when program exits
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_debug-info">
         --debug-info
        </a>
       </td>
       <td>
        Print debugging information, memory, and CPU statistics when program exits
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_default-auth">
         --default-auth
        </a>
       </td>
       <td>
        Authentication plugin to use
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_defaults-extra-file">
         --defaults-extra-file
        </a>
       </td>
       <td>
        Read named option file in addition to usual option files
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_defaults-file">
         --defaults-file
        </a>
       </td>
       <td>
        Read only named option file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_defaults-group-suffix">
         --defaults-group-suffix
        </a>
       </td>
       <td>
        Option group suffix value
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_disable-log-bin">
         --disable-log-bin
        </a>
       </td>
       <td>
        Disable binary logging
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_exclude-gtids">
         --exclude-gtids
        </a>
       </td>
       <td>
        Do not show any of the groups in the GTID set provided
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_force-if-open">
         --force-if-open
        </a>
       </td>
       <td>
        Read binary log files even if open or not closed properly
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_force-read">
         --force-read
        </a>
       </td>
       <td>
        If mysqlbinlog reads a binary log event that it does not recognize, it prints a warning
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_get-server-public-key">
         --get-server-public-key
        </a>
       </td>
       <td>
        Request RSA public key from server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_help">
         --help
        </a>
       </td>
       <td>
        Display help message and exit
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_hexdump">
         --hexdump
        </a>
       </td>
       <td>
        Display a hex dump of the log in comments
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_host">
         --host
        </a>
       </td>
       <td>
        Host on which MySQL server is located
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_idempotent">
         --idempotent
        </a>
       </td>
       <td>
        Cause the server to use idempotent mode while processing binary log updates from this session only
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_include-gtids">
         --include-gtids
        </a>
       </td>
       <td>
        Show only the groups in the GTID set provided
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_local-load">
         --local-load
        </a>
       </td>
       <td>
        Prepare local temporary files for LOAD DATA in the specified directory
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_login-path">
         --login-path
        </a>
       </td>
       <td>
        Read login path options from .mylogin.cnf
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_no-defaults">
         --no-defaults
        </a>
       </td>
       <td>
        Read no option files
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_no-login-paths">
         --no-login-paths
        </a>
       </td>
       <td>
        Do not read login paths from the login path file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_offset">
         --offset
        </a>
       </td>
       <td>
        Skip the first N entries in the log
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_password">
         --password
        </a>
       </td>
       <td>
        Password to use when connecting to server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_plugin-dir">
         --plugin-dir
        </a>
       </td>
       <td>
        Directory where plugins are installed
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_port">
         --port
        </a>
       </td>
       <td>
        TCP/IP port number for connection
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_print-defaults">
         --print-defaults
        </a>
       </td>
       <td>
        Print default options
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_print-table-metadata">
         --print-table-metadata
        </a>
       </td>
       <td>
        Print table metadata
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_protocol">
         --protocol
        </a>
       </td>
       <td>
        Transport protocol to use
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
         --raw
        </a>
       </td>
       <td>
        Write events in raw (binary) format to output files
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-master">
         --read-from-remote-master
        </a>
       </td>
       <td>
        Read the binary log from a MySQL replication source server rather than reading a local log file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
         --read-from-remote-server
        </a>
       </td>
       <td>
        Read binary log from MySQL server rather than local log file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-source">
         --read-from-remote-source
        </a>
       </td>
       <td>
        Read the binary log from a MySQL replication source server rather than reading a local log file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_require-row-format">
         --require-row-format
        </a>
       </td>
       <td>
        Require row-based binary logging format
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_result-file">
         --result-file
        </a>
       </td>
       <td>
        Direct output to named file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_rewrite-db">
         --rewrite-db
        </a>
       </td>
       <td>
        Create rewrite rules for databases when playing back from logs written in row-based format. Can be used multiple times
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-id">
         --server-id
        </a>
       </td>
       <td>
        Extract only those events created by the server having the given server ID
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-id-bits">
         --server-id-bits
        </a>
       </td>
       <td>
        Tell mysqlbinlog how to interpret server IDs in binary log when log was written by a mysqld having its server-id-bits set to less than the maximum; supported only by MySQL Cluster version of mysqlbinlog
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-public-key-path">
         --server-public-key-path
        </a>
       </td>
       <td>
        Path name to file containing RSA public key
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_set-charset">
         --set-charset
        </a>
       </td>
       <td>
        Add a SET NAMES charset_name statement to the output
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_shared-memory-base-name">
         --shared-memory-base-name
        </a>
       </td>
       <td>
        Shared-memory name for shared-memory connections (Windows only)
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_short-form">
         --short-form
        </a>
       </td>
       <td>
        Display only the statements contained in the log
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_skip-gtids">
         --skip-gtids
        </a>
       </td>
       <td>
        Do not include the GTIDs from the binary log files in the output dump file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_socket">
         --socket
        </a>
       </td>
       <td>
        Unix socket file or Windows named pipe to use
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-ca
        </a>
       </td>
       <td>
        File that contains list of trusted SSL Certificate Authorities
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-capath
        </a>
       </td>
       <td>
        Directory that contains trusted SSL Certificate Authority certificate files
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-cert
        </a>
       </td>
       <td>
        File that contains X.509 certificate
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-cipher
        </a>
       </td>
       <td>
        Permissible ciphers for connection encryption
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-crl
        </a>
       </td>
       <td>
        File that contains certificate revocation lists
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-crlpath
        </a>
       </td>
       <td>
        Directory that contains certificate revocation-list files
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl-fips-mode">
         --ssl-fips-mode
        </a>
       </td>
       <td>
        Whether to enable FIPS mode on client side
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-key
        </a>
       </td>
       <td>
        File that contains X.509 key
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-mode
        </a>
       </td>
       <td>
        Desired security state of connection to server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-session-data
        </a>
       </td>
       <td>
        File that contains SSL session data
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl">
         --ssl-session-data-continue-on-failed-reuse
        </a>
       </td>
       <td>
        Whether to establish connections if session reuse fails
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_start-datetime">
         --start-datetime
        </a>
       </td>
       <td>
        Read binary log from first event with timestamp equal to or later than datetime argument
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_start-position">
         --start-position
        </a>
       </td>
       <td>
        Decode binary log from first event with position equal to or greater than argument
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-datetime">
         --stop-datetime
        </a>
       </td>
       <td>
        Stop reading binary log at first event with timestamp equal to or greater than datetime argument
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never">
         --stop-never
        </a>
       </td>
       <td>
        Stay connected to server after reading last binary log file
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never-slave-server-id">
         --stop-never-slave-server-id
        </a>
       </td>
       <td>
        Slave server ID to report when connecting to server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-position">
         --stop-position
        </a>
       </td>
       <td>
        Stop decoding binary log at first event with position equal to or greater than argument
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_tls-ciphersuites">
         --tls-ciphersuites
        </a>
       </td>
       <td>
        Permissible TLSv1.3 ciphersuites for encrypted connections
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_tls-sni-servername">
         --tls-sni-servername
        </a>
       </td>
       <td>
        Server name supplied by the client
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_tls-version">
         --tls-version
        </a>
       </td>
       <td>
        Permissible TLS protocols for encrypted connections
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_to-last-log">
         --to-last-log
        </a>
       </td>
       <td>
        Do not stop at the end of requested binary log from a MySQL server, but rather continue printing to end of last binary log
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_user">
         --user
        </a>
       </td>
       <td>
        MySQL user name to use when connecting to server
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verbose">
         --verbose
        </a>
       </td>
       <td>
        Reconstruct row events as SQL statements
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verify-binlog-checksum">
         --verify-binlog-checksum
        </a>
       </td>
       <td>
        Verify checksums in binary log
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_version">
         --version
        </a>
       </td>
       <td>
        Display version information and exit
       </td>
      </tr>
      <tr>
       <td>
        <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_zstd-compression-level">
         --zstd-compression-level
        </a>
       </td>
       <td>
        Compression level for connections to server that use zstd compression
       </td>
      </tr>
     </tbody>
    </table>
   </div>
   <div class="table-contents">
    <table cellpadding="0" cellspacing="0" style="position: fixed; top: 0px; display: none; left: 401px; width: 739px;">
     <thead>
      <tr>
       <th style="width: 260.906px;">
        Option Name
       </th>
       <th style="width: 477.094px;">
        Description
       </th>
      </tr>
     </thead>
    </table>
   </div>
  </div>
  <br class="table-break"/>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_help">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_help">
       <code class="option">
        --help
       </code>
      </a>
      ,
      <code class="option">
       -?
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for help">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --help
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304952784">
     </a>
     <a class="indexterm" name="idm46045304951296">
     </a>
     <p>
      Display a help message and exit.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_base64-output">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_base64-output">
       <code class="option">
        --base64-output=
        <em class="replaceable">
         <code>
          value
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for base64-output">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --base64-output=value
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           AUTO
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Valid Values
         </th>
         <td>
          <p class="valid-value">
           <code class="literal">
            AUTO
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            NEVER
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            DECODE-ROWS
           </code>
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304932080">
     </a>
     <a class="indexterm" name="idm46045304930592">
     </a>
     <p>
      This option determines when events should be displayed
            encoded as base-64 strings using
      <a class="link" href="binlog.html" title="15.7.8.1 BINLOG Statement">
       <code class="literal">
        BINLOG
       </code>
      </a>
      statements. The option
            has these permissible values (not case-sensitive):
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <code class="literal">
          AUTO
         </code>
         ("automatic") or
         <code class="literal">
          UNSPEC
         </code>
         ("unspecified") displays
         <a class="link" href="binlog.html" title="15.7.8.1 BINLOG Statement">
          <code class="literal">
           BINLOG
          </code>
         </a>
         statements
                automatically when necessary (that is, for format
                description events and row events). If no
         <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_base64-output">
          <code class="option">
           --base64-output
          </code>
         </a>
         option is given, the effect is the same as
         <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_base64-output">
          <code class="option">
           --base64-output=AUTO
          </code>
         </a>
         .
        </p>
        <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
         <div class="admon-title">
          Note
         </div>
         <p>
          Automatic
          <a class="link" href="binlog.html" title="15.7.8.1 BINLOG Statement">
           <code class="literal">
            BINLOG
           </code>
          </a>
          display is the only safe behavior if you intend to use
                  the output of
          <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
           <span class="command">
            <strong>
             mysqlbinlog
            </strong>
           </span>
          </a>
          to
                  re-execute binary log file contents. The other option
                  values are intended only for debugging or testing
                  purposes because they may produce output that does not
                  include all events in executable form.
         </p>
        </div>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          NEVER
         </code>
         causes
         <a class="link" href="binlog.html" title="15.7.8.1 BINLOG Statement">
          <code class="literal">
           BINLOG
          </code>
         </a>
         statements not to
                be displayed.
         <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
          <span class="command">
           <strong>
            mysqlbinlog
           </strong>
          </span>
         </a>
         exits with
                an error if a row event is found that must be displayed
                using
         <a class="link" href="binlog.html" title="15.7.8.1 BINLOG Statement">
          <code class="literal">
           BINLOG
          </code>
         </a>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          DECODE-ROWS
         </code>
         specifies to
         <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
          <span class="command">
           <strong>
            mysqlbinlog
           </strong>
          </span>
         </a>
         that you intend for row
                events to be decoded and displayed as commented SQL
                statements by also specifying the
         <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verbose">
          <code class="option">
           --verbose
          </code>
         </a>
         option.
                Like
         <code class="literal">
          NEVER
         </code>
         ,
         <code class="literal">
          DECODE-ROWS
         </code>
         suppresses display of
         <a class="link" href="binlog.html" title="15.7.8.1 BINLOG Statement">
          <code class="literal">
           BINLOG
          </code>
         </a>
         statements, but
                unlike
         <code class="literal">
          NEVER
         </code>
         , it does not exit with
                an error if a row event is found.
        </p>
       </li>
      </ul>
     </div>
     <p>
      For examples that show the effect of
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_base64-output">
       <code class="option">
        --base64-output
       </code>
      </a>
      and
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verbose">
       <code class="option">
        --verbose
       </code>
      </a>
      on row event
            output, see
      <a class="xref" href="mysqlbinlog-row-events.html" title="6.6.9.2 mysqlbinlog Row Event Display">
       Section 6.6.9.2, “mysqlbinlog Row Event Display”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_bind-address">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_bind-address">
       <code class="option">
        --bind-address=
        <em class="replaceable">
         <code>
          ip_address
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for bind-address">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --bind-address=ip_address
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304893488">
     </a>
     <a class="indexterm" name="idm46045304892000">
     </a>
     <p>
      On a computer having multiple network interfaces, use this
            option to select which interface to use for connecting to
            the MySQL server.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_binlog-row-event-max-size">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_binlog-row-event-max-size">
       <code class="option">
        --binlog-row-event-max-size=
        <em class="replaceable">
         <code>
          N
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for binlog-row-event-max-size">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --binlog-row-event-max-size=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           4294967040
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           256
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           18446744073709547520
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304872512">
     </a>
     <a class="indexterm" name="idm46045304871008">
     </a>
     <p>
      Specify the maximum size of a row-based binary log event, in
            bytes. Rows are grouped into events smaller than this size
            if possible. The value should be a multiple of 256. The
            default is 4GB.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_character-sets-dir">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_character-sets-dir">
       <code class="option">
        --character-sets-dir=
        <em class="replaceable">
         <code>
          dir_name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for character-sets-dir">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --character-sets-dir=dir_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Directory name
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304858848">
     </a>
     <a class="indexterm" name="idm46045304857344">
     </a>
     <p>
      The directory where character sets are installed. See
      <a class="xref" href="charset-configuration.html" title="12.15 Character Set Configuration">
       Section 12.15, “Character Set Configuration”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_compress">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_compress">
       <code class="option">
        --compress
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for compress">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --compress[={OFF|ON}]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Deprecated
         </th>
         <td>
          Yes
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           OFF
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304840464">
     </a>
     <a class="indexterm" name="idm46045304838976">
     </a>
     <p>
      Compress all information sent between the client and the
            server if possible. See
      <a class="xref" href="connection-compression-control.html" title="6.2.8 Connection Compression Control">
       Section 6.2.8, “Connection Compression Control”
      </a>
      .
     </p>
     <p>
      This option is deprecated. Expect it to be removed in a
            future version of MySQL. See
      <a class="xref" href="connection-compression-control.html#connection-compression-legacy-configuration" title="Configuring Legacy Connection Compression">
       Configuring Legacy Connection Compression
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_compression-algorithms">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_compression-algorithms">
       <code class="option">
        --compression-algorithms=
        <em class="replaceable">
         <code>
          value
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for compression-algorithms">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --compression-algorithms=value
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Set
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           uncompressed
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Valid Values
         </th>
         <td>
          <p class="valid-value">
           <code class="literal">
            zlib
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            zstd
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            uncompressed
           </code>
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304817664">
     </a>
     <a class="indexterm" name="idm46045304816160">
     </a>
     <p>
      The permitted compression algorithms for connections to the
            server. The available algorithms are the same as for the
      <a class="link" href="server-system-variables.html#sysvar_protocol_compression_algorithms">
       <code class="literal">
        protocol_compression_algorithms
       </code>
      </a>
      system variable. The default value is
      <code class="literal">
       uncompressed
      </code>
      .
     </p>
     <p>
      For more information, see
      <a class="xref" href="connection-compression-control.html" title="6.2.8 Connection Compression Control">
       Section 6.2.8, “Connection Compression Control”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_connection-server-id">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_connection-server-id">
       <code class="option">
        --connection-server-id=
        <em class="replaceable">
         <code>
          server_id
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for connection-server-id">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --connection-server-id=#]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           0 (1)
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           0 (1)
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           4294967295
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304793616">
     </a>
     <a class="indexterm" name="idm46045304792112">
     </a>
     <p>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_connection-server-id">
       <code class="option">
        --connection-server-id
       </code>
      </a>
      specifies the server ID that
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      reports when it connects to the server. It can be used to
            avoid a conflict with the ID of a replica server or another
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      process.
     </p>
     <p>
      If the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
       <code class="option">
        --read-from-remote-server
       </code>
      </a>
      option is specified,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      reports
            a server ID of 0, which tells the server to disconnect after
            sending the last log file (nonblocking behavior). If the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never">
       <code class="option">
        --stop-never
       </code>
      </a>
      option is
            also specified to maintain the connection to the server,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      reports a server ID of 1 by
            default instead of 0, and
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_connection-server-id">
       <code class="option">
        --connection-server-id
       </code>
      </a>
      can be used to replace that server ID if required. See
      <a class="xref" href="mysqlbinlog-server-id.html" title="6.6.9.4 Specifying the mysqlbinlog Server ID">
       Section 6.6.9.4, “Specifying the mysqlbinlog Server ID”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_database">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_database">
       <code class="option">
        --database=
        <em class="replaceable">
         <code>
          db_name
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -d
       <em class="replaceable">
        <code>
         db_name
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for database">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --database=db_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304768736">
     </a>
     <a class="indexterm" name="idm46045304767248">
     </a>
     <p>
      This option causes
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      to output
            entries from the binary log (local log only) that occur
            while
      <em class="replaceable">
       <code>
        db_name
       </code>
      </em>
      is been selected as
            the default database by
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE
       </code>
      </a>
      .
     </p>
     <p>
      The
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_database">
       <code class="option">
        --database
       </code>
      </a>
      option
            for
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      is similar to the
      <a class="link" href="replication-options-binary-log.html#option_mysqld_binlog-do-db">
       <code class="option">
        --binlog-do-db
       </code>
      </a>
      option for
      <a class="link" href="mysqld.html" title="6.3.1 mysqld — The MySQL Server">
       <span class="command">
        <strong>
         mysqld
        </strong>
       </span>
      </a>
      , but can be used to specify only
            one database. If
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_database">
       <code class="option">
        --database
       </code>
      </a>
      is given
            multiple times, only the last instance is used.
     </p>
     <p>
      The effects of this option depend on whether the
            statement-based or row-based logging format is in use, in
            the same way that the effects of
      <a class="link" href="replication-options-binary-log.html#option_mysqld_binlog-do-db">
       <code class="option">
        --binlog-do-db
       </code>
      </a>
      depend on
            whether statement-based or row-based logging is in use.
     </p>
     <p>
      <b>
       Statement-based logging.
      </b>
      The
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_database">
       <code class="option">
        --database
       </code>
      </a>
      option
              works as follows:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         While
         <em class="replaceable">
          <code>
           db_name
          </code>
         </em>
         is the default
                database, statements are output whether they modify
                tables in
         <em class="replaceable">
          <code>
           db_name
          </code>
         </em>
         or a
                different database.
        </p>
       </li>
       <li class="listitem">
        <p>
         Unless
         <em class="replaceable">
          <code>
           db_name
          </code>
         </em>
         is selected as
                the default database, statements are not output, even if
                they modify tables in
         <em class="replaceable">
          <code>
           db_name
          </code>
         </em>
         .
        </p>
       </li>
       <li class="listitem">
        <p>
         There is an exception for
         <a class="link" href="create-database.html" title="15.1.12 CREATE DATABASE Statement">
          <code class="literal">
           CREATE
                DATABASE
          </code>
         </a>
         ,
         <a class="link" href="alter-database.html" title="15.1.2 ALTER DATABASE Statement">
          <code class="literal">
           ALTER
                DATABASE
          </code>
         </a>
         , and
         <a class="link" href="drop-database.html" title="15.1.24 DROP DATABASE Statement">
          <code class="literal">
           DROP
                DATABASE
          </code>
         </a>
         . The database being
         <span class="emphasis">
          <em>
           created, altered, or dropped
          </em>
         </span>
         is
                considered to be the default database when determining
                whether to output the statement.
        </p>
       </li>
      </ul>
     </div>
     <p>
      Suppose that the binary log was created by executing these
            statements using statement-based-logging:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-sql"><div class="docs-select-all right" id="sa77013981"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-sql"><span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> test<span class="token punctuation">.</span>t1 <span class="token punctuation">(</span>i<span class="token punctuation">)</span> <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">100</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
<span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> db2<span class="token punctuation">.</span>t2 <span class="token punctuation">(</span>j<span class="token punctuation">)</span>  <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">200</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
<span class="token keyword">USE</span> test<span class="token punctuation">;</span>
<span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> test<span class="token punctuation">.</span>t1 <span class="token punctuation">(</span>i<span class="token punctuation">)</span> <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">101</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
<span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> t1 <span class="token punctuation">(</span>i<span class="token punctuation">)</span>      <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">102</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
<span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> db2<span class="token punctuation">.</span>t2 <span class="token punctuation">(</span>j<span class="token punctuation">)</span>  <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">201</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
<span class="token keyword">USE</span> db2<span class="token punctuation">;</span>
<span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> test<span class="token punctuation">.</span>t1 <span class="token punctuation">(</span>i<span class="token punctuation">)</span> <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">103</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
<span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> db2<span class="token punctuation">.</span>t2 <span class="token punctuation">(</span>j<span class="token punctuation">)</span>  <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">202</span><span class="token punctuation">)</span><span class="token punctuation">;</span>
<span class="token keyword">INSERT</span> <span class="token keyword">INTO</span> t2 <span class="token punctuation">(</span>j<span class="token punctuation">)</span>      <span class="token keyword">VALUES</span><span class="token punctuation">(</span><span class="token number">203</span><span class="token punctuation">)</span><span class="token punctuation">;</span></code></pre>
     </div>
     <p>
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog --database=test
        </strong>
       </span>
      </a>
      does not
            output the first two
      <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
       <code class="literal">
        INSERT
       </code>
      </a>
      statements because there is no default database. It outputs
            the three
      <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
       <code class="literal">
        INSERT
       </code>
      </a>
      statements
            following
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE
            test
       </code>
      </a>
      , but not the three
      <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
       <code class="literal">
        INSERT
       </code>
      </a>
      statements following
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE db2
       </code>
      </a>
      .
     </p>
     <p>
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog --database=db2
        </strong>
       </span>
      </a>
      does not
            output the first two
      <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
       <code class="literal">
        INSERT
       </code>
      </a>
      statements because there is no default database. It does not
            output the three
      <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
       <code class="literal">
        INSERT
       </code>
      </a>
      statements following
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE test
       </code>
      </a>
      , but
            does output the three
      <a class="link" href="insert.html" title="15.2.7 INSERT Statement">
       <code class="literal">
        INSERT
       </code>
      </a>
      statements following
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE db2
       </code>
      </a>
      .
     </p>
     <p>
      <b>
       Row-based logging.
      </b>
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      outputs only entries that
              change tables belonging to
      <em class="replaceable">
       <code>
        db_name
       </code>
      </em>
      . The default database
              has no effect on this. Suppose that the binary log just
              described was created using row-based logging rather than
              statement-based logging.
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
              --database=test
        </strong>
       </span>
      </a>
      outputs only those entries that
              modify
      <code class="literal">
       t1
      </code>
      in the test database,
              regardless of whether
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE
       </code>
      </a>
      was issued or what the default database is.
     </p>
     <p>
      If a server is running with
      <a class="link" href="replication-options-binary-log.html#sysvar_binlog_format">
       <code class="literal">
        binlog_format
       </code>
      </a>
      set to
      <code class="literal">
       MIXED
      </code>
      and you want it to be possible to
            use
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      with the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_database">
       <code class="option">
        --database
       </code>
      </a>
      option, you
            must ensure that tables that are modified are in the
            database selected by
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE
       </code>
      </a>
      . (In
            particular, no cross-database updates should be used.)
     </p>
     <p>
      When used together with the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_rewrite-db">
       <code class="option">
        --rewrite-db
       </code>
      </a>
      option, the
      <code class="option">
       --rewrite-db
      </code>
      option is applied first; then
            the
      <code class="option">
       --database
      </code>
      option is applied, using the
            rewritten database name. The order in which the options are
            provided makes no difference in this regard.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_debug">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_debug">
       <code class="option">
        --debug[=
        <em class="replaceable">
         <code>
          debug_options
         </code>
        </em>
        ]
       </code>
      </a>
      ,
      <code class="option">
       -#
            [
       <em class="replaceable">
        <code>
         debug_options
        </code>
       </em>
       ]
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for debug">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --debug[=debug_options]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           d:t:o,/tmp/mysqlbinlog.trace
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304697104">
     </a>
     <a class="indexterm" name="idm46045304695616">
     </a>
     <p>
      Write a debugging log. A typical
      <em class="replaceable">
       <code>
        debug_options
       </code>
      </em>
      string is
      <code class="literal">
       d:t:o,
       <em class="replaceable">
        <code>
         file_name
        </code>
       </em>
      </code>
      .
            The default is
      <code class="literal">
       d:t:o,/tmp/mysqlbinlog.trace
      </code>
      .
     </p>
     <p>
      This option is available only if MySQL was built using
      <a class="link" href="source-configuration-options.html#option_cmake_with_debug">
       <code class="option">
        WITH_DEBUG
       </code>
      </a>
      . MySQL release
            binaries provided by Oracle are
      <span class="emphasis">
       <em>
        not
       </em>
      </span>
      built using this option.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_debug-check">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_debug-check">
       <code class="option">
        --debug-check
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for debug-check">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --debug-check
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           FALSE
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304677360">
     </a>
     <a class="indexterm" name="idm46045304675872">
     </a>
     <p>
      Print some debugging information when the program exits.
     </p>
     <p>
      This option is available only if MySQL was built using
      <a class="link" href="source-configuration-options.html#option_cmake_with_debug">
       <code class="option">
        WITH_DEBUG
       </code>
      </a>
      . MySQL release
            binaries provided by Oracle are
      <span class="emphasis">
       <em>
        not
       </em>
      </span>
      built using this option.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_debug-info">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_debug-info">
       <code class="option">
        --debug-info
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for debug-info">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --debug-info
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           FALSE
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304659760">
     </a>
     <a class="indexterm" name="idm46045304658272">
     </a>
     <p>
      Print debugging information and memory and CPU usage
            statistics when the program exits.
     </p>
     <p>
      This option is available only if MySQL was built using
      <a class="link" href="source-configuration-options.html#option_cmake_with_debug">
       <code class="option">
        WITH_DEBUG
       </code>
      </a>
      . MySQL release
            binaries provided by Oracle are
      <span class="emphasis">
       <em>
        not
       </em>
      </span>
      built using this option.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_default-auth">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_default-auth">
       <code class="option">
        --default-auth=
        <em class="replaceable">
         <code>
          plugin
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for default-auth">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --default-auth=plugin
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304644336">
     </a>
     <a class="indexterm" name="idm46045304642848">
     </a>
     <p>
      A hint about which client-side authentication plugin to use.
            See
      <a class="xref" href="pluggable-authentication.html" title="8.2.17 Pluggable Authentication">
       Section 8.2.17, “Pluggable Authentication”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_defaults-extra-file">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_defaults-extra-file">
       <code class="option">
        --defaults-extra-file=
        <em class="replaceable">
         <code>
          file_name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for defaults-extra-file">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --defaults-extra-file=file_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          File name
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304630160">
     </a>
     <a class="indexterm" name="idm46045304628656">
     </a>
     <p>
      Read this option file after the global option file but (on
            Unix) before the user option file. If the file does not
            exist or is otherwise inaccessible, an error occurs. If
      <em class="replaceable">
       <code>
        file_name
       </code>
      </em>
      is not an absolute path
            name, it is interpreted relative to the current directory.
     </p>
     <p>
      For additional information about this and other option-file
            options, see
      <a class="xref" href="option-file-options.html" title="6.2.2.3 Command-Line Options that Affect Option-File Handling">
       Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_defaults-file">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_defaults-file">
       <code class="option">
        --defaults-file=
        <em class="replaceable">
         <code>
          file_name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for defaults-file">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --defaults-file=file_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          File name
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304614816">
     </a>
     <a class="indexterm" name="idm46045304613328">
     </a>
     <p>
      Use only the given option file. If the file does not exist
            or is otherwise inaccessible, an error occurs. If
      <em class="replaceable">
       <code>
        file_name
       </code>
      </em>
      is not an absolute path
            name, it is interpreted relative to the current directory.
     </p>
     <p>
      Exception: Even with
      <a class="link" href="option-file-options.html#option_general_defaults-file">
       <code class="option">
        --defaults-file
       </code>
      </a>
      , client
            programs read
      <code class="filename">
       .mylogin.cnf
      </code>
      .
     </p>
     <p>
      For additional information about this and other option-file
            options, see
      <a class="xref" href="option-file-options.html" title="6.2.2.3 Command-Line Options that Affect Option-File Handling">
       Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_defaults-group-suffix">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_defaults-group-suffix">
       <code class="option">
        --defaults-group-suffix=
        <em class="replaceable">
         <code>
          str
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for defaults-group-suffix">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --defaults-group-suffix=str
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304597296">
     </a>
     <a class="indexterm" name="idm46045304595792">
     </a>
     <p>
      Read not only the usual option groups, but also groups with
            the usual names and a suffix of
      <em class="replaceable">
       <code>
        str
       </code>
      </em>
      . For example,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      normally reads the
      <code class="literal">
       [client]
      </code>
      and
      <code class="literal">
       [mysqlbinlog]
      </code>
      groups. If this option is
            given as
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_defaults-group-suffix">
       <code class="option">
        --defaults-group-suffix=_other
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      also reads the
      <code class="literal">
       [client_other]
      </code>
      and
      <code class="literal">
       [mysqlbinlog_other]
      </code>
      groups.
     </p>
     <p>
      For additional information about this and other option-file
            options, see
      <a class="xref" href="option-file-options.html" title="6.2.2.3 Command-Line Options that Affect Option-File Handling">
       Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_disable-log-bin">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_disable-log-bin">
       <code class="option">
        --disable-log-bin
       </code>
      </a>
      ,
      <code class="option">
       -D
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for disable-log-bin">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --disable-log-bin
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304577696">
     </a>
     <a class="indexterm" name="idm46045304576208">
     </a>
     <p>
      Disable binary logging. This is useful for avoiding an
            endless loop if you use the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_to-last-log">
       <code class="option">
        --to-last-log
       </code>
      </a>
      option and
            are sending the output to the same MySQL server. This option
            also is useful when restoring after an unexpected exit to
            avoid duplication of the statements you have logged.
     </p>
     <p>
      This option causes
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      to include
            a
      <a class="link" href="set-sql-log-bin.html" title="15.4.1.3 SET sql_log_bin Statement">
       <code class="literal">
        SET
            sql_log_bin = 0
       </code>
      </a>
      statement in its output to disable
            binary logging of the remaining output. Manipulating the
            session value of the
      <a class="link" href="replication-options-binary-log.html#sysvar_sql_log_bin">
       <code class="literal">
        sql_log_bin
       </code>
      </a>
      system variable
            is a restricted operation, so this option requires that you
            have privileges sufficient to set restricted session
            variables. See
      <a class="xref" href="system-variable-privileges.html" title="7.1.9.1 System Variable Privileges">
       Section 7.1.9.1, “System Variable Privileges”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_exclude-gtids">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_exclude-gtids">
       <code class="option">
        --exclude-gtids=
        <em class="replaceable">
         <code>
          gtid_set
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for exclude-gtids">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --exclude-gtids=gtid_set
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304554960">
     </a>
     <a class="indexterm" name="idm46045304553472">
     </a>
     <p>
      Do not display any of the groups listed in the
      <em class="replaceable">
       <code>
        gtid_set
       </code>
      </em>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_force-if-open">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_force-if-open">
       <code class="option">
        --force-if-open
       </code>
      </a>
      ,
      <code class="option">
       -F
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for force-if-open">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --force-if-open
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304542992">
     </a>
     <a class="indexterm" name="idm46045304541504">
     </a>
     <p>
      Read binary log files even if they are open or were not
            closed properly (
      <code class="literal">
       IN_USE
      </code>
      flag is set); do
            not fail if the file ends with a truncated event.
     </p>
     <p>
      The
      <code class="literal">
       IN_USE
      </code>
      flag is set only for the
            binary log that is currently written by the server; if the
            server has crashed, the flag remains set until the server is
            started up again and recovers the binary log. Without this
            option,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      refuses to process a
            file with this flag set. Since the server may be in the
            process of writing the file, truncation of the last event is
            considered normal.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_force-read">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_force-read">
       <code class="option">
        --force-read
       </code>
      </a>
      ,
      <code class="option">
       -f
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for force-read">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --force-read
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304527856">
     </a>
     <a class="indexterm" name="idm46045304526368">
     </a>
     <p>
      With this option, if
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      reads a
            binary log event that it does not recognize, it prints a
            warning, ignores the event, and continues. Without this
            option,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      stops if it reads
            such an event.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_get-server-public-key">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_get-server-public-key">
       <code class="option">
        --get-server-public-key
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for get-server-public-key">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --get-server-public-key
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304511904">
     </a>
     <a class="indexterm" name="idm46045304510400">
     </a>
     <p>
      Request from the server the public key required for RSA key
            pair-based password exchange. This option applies to clients
            that authenticate with the
      <code class="literal">
       caching_sha2_password
      </code>
      authentication
            plugin. For that plugin, the server does not send the public
            key unless requested. This option is ignored for accounts
            that do not authenticate with that plugin. It is also
            ignored if RSA-based password exchange is not used, as is
            the case when the client connects to the server using a
            secure connection.
     </p>
     <p>
      If
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-public-key-path">
       <code class="option">
        --server-public-key-path=
        <em class="replaceable">
         <code>
          file_name
         </code>
        </em>
       </code>
      </a>
      is given and specifies a valid public key file, it takes
            precedence over
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_get-server-public-key">
       <code class="option">
        --get-server-public-key
       </code>
      </a>
      .
     </p>
     <p>
      For information about the
      <code class="literal">
       caching_sha2_password
      </code>
      plugin, see
      <a class="xref" href="caching-sha2-pluggable-authentication.html" title="8.4.1.2 Caching SHA-2 Pluggable Authentication">
       Section 8.4.1.2, “Caching SHA-2 Pluggable Authentication”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_hexdump">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_hexdump">
       <code class="option">
        --hexdump
       </code>
      </a>
      ,
      <code class="option">
       -H
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for hexdump">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --hexdump
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304494400">
     </a>
     <a class="indexterm" name="idm46045304492912">
     </a>
     <p>
      Display a hex dump of the log in comments, as described in
      <a class="xref" href="mysqlbinlog-hexdump.html" title="6.6.9.1 mysqlbinlog Hex Dump Format">
       Section 6.6.9.1, “mysqlbinlog Hex Dump Format”
      </a>
      . The hex output can be
            helpful for replication debugging.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_host">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_host">
       <code class="option">
        --host=
        <em class="replaceable">
         <code>
          host_name
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -h
       <em class="replaceable">
        <code>
         host_name
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for host">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --host=host_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           localhost
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304477024">
     </a>
     <a class="indexterm" name="idm46045304475536">
     </a>
     <p>
      Get the binary log from the MySQL server on the given host.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_idempotent">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_idempotent">
       <code class="option">
        --idempotent
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for idempotent">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --idempotent
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           true
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304461360">
     </a>
     <a class="indexterm" name="idm46045304459872">
     </a>
     <p>
      Tell the MySQL Server to use idempotent mode while
            processing updates; this causes suppression of any
            duplicate-key or key-not-found errors that the server
            encounters in the current session while processing updates.
            This option may prove useful whenever it is desirable or
            necessary to replay one or more binary logs to a MySQL
            Server which may not contain all of the data to which the
            logs refer.
     </p>
     <p>
      The scope of effect for this option includes the current
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      client and session only.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_include-gtids">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_include-gtids">
       <code class="option">
        --include-gtids=
        <em class="replaceable">
         <code>
          gtid_set
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for include-gtids">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --include-gtids=gtid_set
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304443392">
     </a>
     <a class="indexterm" name="idm46045304441904">
     </a>
     <p>
      Display only the groups listed in the
      <em class="replaceable">
       <code>
        gtid_set
       </code>
      </em>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_local-load">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_local-load">
       <code class="option">
        --local-load=
        <em class="replaceable">
         <code>
          dir_name
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -l
       <em class="replaceable">
        <code>
         dir_name
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for local-load">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --local-load=dir_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Directory name
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304428704">
     </a>
     <a class="indexterm" name="idm46045304427216">
     </a>
     <p>
      For data loading operations corresponding to
      <a class="link" href="load-data.html" title="15.2.9 LOAD DATA Statement">
       <code class="literal">
        LOAD DATA
       </code>
      </a>
      statements,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      extracts the files from the
            binary log events, writes them as temporary files to the
            local file system, and writes
      <a class="link" href="load-data.html" title="15.2.9 LOAD DATA Statement">
       <code class="literal">
        LOAD DATA
            LOCAL
       </code>
      </a>
      statements to cause the files to be loaded.
            By default,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      writes these
            temporary files to an operating system-specific directory.
            The
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_local-load">
       <code class="option">
        --local-load
       </code>
      </a>
      option
            can be used to explicitly specify the directory where
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      should prepare local
            temporary files.
     </p>
     <p>
      Because other processes can write files to the default
            system-specific directory, it is advisable to specify the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_local-load">
       <code class="option">
        --local-load
       </code>
      </a>
      option to
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      to designate a different
            directory for data files, and then designate that same
            directory by specifying the
      <a class="link" href="mysql-command-options.html#option_mysql_load-data-local-dir">
       <code class="option">
        --load-data-local-dir
       </code>
      </a>
      option
            to
      <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
       <span class="command">
        <strong>
         mysql
        </strong>
       </span>
      </a>
      when processing the output from
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      . For example:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa59998111"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog <span class="token constant">--local-load</span><span class="token attr-value"><span class="token punctuation">=</span>/my/local/data</span> <span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span>
    | mysql <span class="token constant">--load-data-local-dir</span><span class="token attr-value"><span class="token punctuation">=</span>/my/local/data</span> <span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span></code></pre>
     </div>
     <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Important
      </div>
      <p>
       These temporary files are not automatically removed by
       <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
        <span class="command">
         <strong>
          mysqlbinlog
         </strong>
        </span>
       </a>
       or any other MySQL program.
      </p>
     </div>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_login-path">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_login-path">
       <code class="option">
        --login-path=
        <em class="replaceable">
         <code>
          name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for login-path">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --login-path=name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304398144">
     </a>
     <a class="indexterm" name="idm46045304396656">
     </a>
     <p>
      Read options from the named login path in the
      <code class="filename">
       .mylogin.cnf
      </code>
      login path file. A
      <span class="quote">
       “
       <span class="quote">
        login path
       </span>
       ”
      </span>
      is an option group containing
            options that specify which MySQL server to connect to and
            which account to authenticate as. To create or modify a
            login path file, use the
      <a class="link" href="mysql-config-editor.html" title="6.6.7 mysql_config_editor — MySQL Configuration Utility">
       <span class="command">
        <strong>
         mysql_config_editor
        </strong>
       </span>
      </a>
      utility. See
      <a class="xref" href="mysql-config-editor.html" title="6.6.7 mysql_config_editor — MySQL Configuration Utility">
       Section 6.6.7, “mysql_config_editor — MySQL Configuration Utility”
      </a>
      .
     </p>
     <p>
      For additional information about this and other option-file
            options, see
      <a class="xref" href="option-file-options.html" title="6.2.2.3 Command-Line Options that Affect Option-File Handling">
       Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_no-login-paths">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_no-login-paths">
       <code class="option">
        --no-login-paths
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for no-login-paths">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --no-login-paths
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304382576">
     </a>
     <a class="indexterm" name="idm46045304381088">
     </a>
     <p>
      Skips reading options from the login path file.
     </p>
     <p>
      See
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_login-path">
       <code class="option">
        --login-path
       </code>
      </a>
      for
            related information.
     </p>
     <p>
      For additional information about this and other option-file
            options, see
      <a class="xref" href="option-file-options.html" title="6.2.2.3 Command-Line Options that Affect Option-File Handling">
       Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_no-defaults">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_no-defaults">
       <code class="option">
        --no-defaults
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for no-defaults">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --no-defaults
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304368880">
     </a>
     <a class="indexterm" name="idm46045304367392">
     </a>
     <p>
      Do not read any option files. If program startup fails due
            to reading unknown options from an option file,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_no-defaults">
       <code class="option">
        --no-defaults
       </code>
      </a>
      can be
            used to prevent them from being read.
     </p>
     <p>
      The exception is that the
      <code class="filename">
       .mylogin.cnf
      </code>
      file is read in all cases, if it exists. This permits
            passwords to be specified in a safer way than on the command
            line even when
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_no-defaults">
       <code class="option">
        --no-defaults
       </code>
      </a>
      is used.
            To create
      <code class="filename">
       .mylogin.cnf
      </code>
      , use the
      <a class="link" href="mysql-config-editor.html" title="6.6.7 mysql_config_editor — MySQL Configuration Utility">
       <span class="command">
        <strong>
         mysql_config_editor
        </strong>
       </span>
      </a>
      utility. See
      <a class="xref" href="mysql-config-editor.html" title="6.6.7 mysql_config_editor — MySQL Configuration Utility">
       Section 6.6.7, “mysql_config_editor — MySQL Configuration Utility”
      </a>
      .
     </p>
     <p>
      For additional information about this and other option-file
            options, see
      <a class="xref" href="option-file-options.html" title="6.2.2.3 Command-Line Options that Affect Option-File Handling">
       Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_offset">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_offset">
       <code class="option">
        --offset=
        <em class="replaceable">
         <code>
          N
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -o
       <em class="replaceable">
        <code>
         N
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for offset">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --offset=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304347536">
     </a>
     <a class="indexterm" name="idm46045304346048">
     </a>
     <p>
      Skip the first
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      entries in the
            log.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_open-files-limit">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_open-files-limit">
       <code class="option">
        --open-files-limit=
        <em class="replaceable">
         <code>
          N
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for open-files-limit">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --open-files-limit=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           8
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           [platform dependent]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304326384">
     </a>
     <a class="indexterm" name="idm46045304324896">
     </a>
     <a class="indexterm" name="idm46045304323408">
     </a>
     <p>
      Specify the number of open file descriptors to reserve.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_password">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_password">
       <code class="option">
        --password[=
        <em class="replaceable">
         <code>
          password
         </code>
        </em>
        ]
       </code>
      </a>
      ,
      <code class="option">
       -p[
       <em class="replaceable">
        <code>
         password
        </code>
       </em>
       ]
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for password">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --password[=password]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304310464">
     </a>
     <a class="indexterm" name="idm46045304308976">
     </a>
     <p>
      The password of the MySQL account used for connecting to the
            server. The password value is optional. If not given,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      prompts for one. If given,
            there must be
      <span class="emphasis">
       <em>
        no space
       </em>
      </span>
      between
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_password">
       <code class="option">
        --password=
       </code>
      </a>
      or
      <code class="option">
       -p
      </code>
      and the password following it. If no
            password option is specified, the default is to send no
            password.
     </p>
     <p>
      Specifying a password on the command line should be
            considered insecure. To avoid giving the password on the
            command line, use an option file. See
      <a class="xref" href="password-security-user.html" title="8.1.2.1 End-User Guidelines for Password Security">
       Section 8.1.2.1, “End-User Guidelines for Password Security”
      </a>
      .
     </p>
     <p>
      To explicitly specify that there is no password and that
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      should not prompt for one,
            use the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_password">
       <code class="option">
        --skip-password
       </code>
      </a>
      option.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_plugin-dir">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_plugin-dir">
       <code class="option">
        --plugin-dir=
        <em class="replaceable">
         <code>
          dir_name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for plugin-dir">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --plugin-dir=dir_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Directory name
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304289648">
     </a>
     <a class="indexterm" name="idm46045304288160">
     </a>
     <p>
      The directory in which to look for plugins. Specify this
            option if the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_default-auth">
       <code class="option">
        --default-auth
       </code>
      </a>
      option is
            used to specify an authentication plugin but
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      does not find it. See
      <a class="xref" href="pluggable-authentication.html" title="8.2.17 Pluggable Authentication">
       Section 8.2.17, “Pluggable Authentication”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_port">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_port">
       <code class="option">
        --port=
        <em class="replaceable">
         <code>
          port_num
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -P
       <em class="replaceable">
        <code>
         port_num
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for port">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --port=port_num
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           3306
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304270032">
     </a>
     <a class="indexterm" name="idm46045304268544">
     </a>
     <a class="indexterm" name="idm46045304267056">
     </a>
     <a class="indexterm" name="idm46045304265984">
     </a>
     <p>
      The TCP/IP port number to use for connecting to a remote
            server.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_print-defaults">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_print-defaults">
       <code class="option">
        --print-defaults
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print-defaults">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print-defaults
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304256704">
     </a>
     <a class="indexterm" name="idm46045304255216">
     </a>
     <p>
      Print the program name and all options that it gets from
            option files.
     </p>
     <p>
      For additional information about this and other option-file
            options, see
      <a class="xref" href="option-file-options.html" title="6.2.2.3 Command-Line Options that Affect Option-File Handling">
       Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_print-table-metadata">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_print-table-metadata">
       <code class="option">
        --print-table-metadata
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for print-table-metadata">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --print-table-metadata
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304244400">
     </a>
     <a class="indexterm" name="idm46045304242896">
     </a>
     <p>
      Print table related metadata from the binary log. Configure
            the amount of table related metadata binary logged using
      <a class="link" href="replication-options-binary-log.html#sysvar_binlog_row_metadata">
       <code class="literal">
        binlog-row-metadata
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_protocol">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_protocol">
       <code class="option">
        --protocol={TCP|SOCKET|PIPE|MEMORY}
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for protocol">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --protocol=type
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [see text]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Valid Values
         </th>
         <td>
          <p class="valid-value">
           <code class="literal">
            TCP
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            SOCKET
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            PIPE
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            MEMORY
           </code>
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304221536">
     </a>
     <a class="indexterm" name="idm46045304220048">
     </a>
     <p>
      The transport protocol to use for connecting to the server.
            It is useful when the other connection parameters normally
            result in use of a protocol other than the one you want. For
            details on the permissible values, see
      <a class="xref" href="transport-protocols.html" title="6.2.7 Connection Transport Protocols">
       Section 6.2.7, “Connection Transport Protocols”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_raw">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
       <code class="option">
        --raw
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for raw">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --raw
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           FALSE
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304205136">
     </a>
     <a class="indexterm" name="idm46045304203648">
     </a>
     <p>
      By default,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      reads binary log
            files and writes events in text format. The
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
       <code class="option">
        --raw
       </code>
      </a>
      option tells
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      to write them in their
            original binary format. Its use requires that
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
       <code class="option">
        --read-from-remote-server
       </code>
      </a>
      also be used because the files are requested from a server.
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      writes one output file for
            each file read from the server. The
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
       <code class="option">
        --raw
       </code>
      </a>
      option can be used
            to make a backup of a server's binary log. With the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never">
       <code class="option">
        --stop-never
       </code>
      </a>
      option, the
            backup is
      <span class="quote">
       “
       <span class="quote">
        live
       </span>
       ”
      </span>
      because
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      stays connected to the
            server. By default, output files are written in the current
            directory with the same names as the original log files.
            Output file names can be modified using the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_result-file">
       <code class="option">
        --result-file
       </code>
      </a>
      option.
            For more information, see
      <a class="xref" href="mysqlbinlog-backup.html" title="6.6.9.3 Using mysqlbinlog to Back Up Binary Log Files">
       Section 6.6.9.3, “Using mysqlbinlog to Back Up Binary Log Files”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_read-from-remote-source">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-source">
       <code class="option">
        --read-from-remote-source=
        <em class="replaceable">
         <code>
          type
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for read-from-remote-source">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --read-from-remote-source=type
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304181728">
     </a>
     <a class="indexterm" name="idm46045304180224">
     </a>
     <p>
      This option reads binary logs from a MySQL server with the
      <code class="literal">
       COM_BINLOG_DUMP
      </code>
      or
      <code class="literal">
       COM_BINLOG_DUMP_GTID
      </code>
      commands by setting
            the option value to either
      <code class="literal">
       BINLOG-DUMP-NON-GTIDS
      </code>
      or
      <code class="literal">
       BINLOG-DUMP-GTIDS
      </code>
      , respectively. If
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-source">
       <code class="option">
        --read-from-remote-source=BINLOG-DUMP-GTIDS
       </code>
      </a>
      is combined with
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_exclude-gtids">
       <code class="option">
        --exclude-gtids
       </code>
      </a>
      ,
            transactions can be filtered out on the source, avoiding
            unnecessary network traffic.
     </p>
     <p>
      The connection parameter options are used with these options
            or the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
       <code class="option">
        --read-from-remote-server
       </code>
      </a>
      option. These options are
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_host">
       <code class="option">
        --host
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_password">
       <code class="option">
        --password
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_port">
       <code class="option">
        --port
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_protocol">
       <code class="option">
        --protocol
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_socket">
       <code class="option">
        --socket
       </code>
      </a>
      , and
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_user">
       <code class="option">
        --user
       </code>
      </a>
      . If none of the
            remote options is specified, the connection parameter
            options are ignored.
     </p>
     <p>
      The
      <a class="link" href="privileges-provided.html#priv_replication-slave">
       <code class="literal">
        REPLICATION SLAVE
       </code>
      </a>
      privilege is required to use these options.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_read-from-remote-master">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-master">
       <code class="option">
        --read-from-remote-master=
        <em class="replaceable">
         <code>
          type
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for read-from-remote-master">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --read-from-remote-master=type
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Deprecated
         </th>
         <td>
          Yes
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304153616">
     </a>
     <a class="indexterm" name="idm46045304152112">
     </a>
     <p>
      Deprecated synonym for
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-source">
       <code class="option">
        --read-from-remote-source
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_read-from-remote-server">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
       <code class="option">
        --read-from-remote-server=
        <em class="replaceable">
         <code>
          file_name
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -R
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for read-from-remote-server">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --read-from-remote-server=file_name
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304140608">
     </a>
     <a class="indexterm" name="idm46045304139104">
     </a>
     <p>
      Read the binary log from a MySQL server rather than reading
            a local log file. This option requires that the remote
            server be running. It works only for binary log files on the
            remote server and not relay log files. This accepts the
            binary log file name (including the numeric suffix) without
            the file path.
     </p>
     <p>
      The connection parameter options are used with this option
            or the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-source">
       <code class="option">
        --read-from-remote-source
       </code>
      </a>
      option. These options are
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_host">
       <code class="option">
        --host
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_password">
       <code class="option">
        --password
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_port">
       <code class="option">
        --port
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_protocol">
       <code class="option">
        --protocol
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_socket">
       <code class="option">
        --socket
       </code>
      </a>
      , and
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_user">
       <code class="option">
        --user
       </code>
      </a>
      . If neither of
            the remote options is specified, the connection parameter
            options are ignored.
     </p>
     <p>
      The
      <a class="link" href="privileges-provided.html#priv_replication-slave">
       <code class="literal">
        REPLICATION SLAVE
       </code>
      </a>
      privilege is required to use this option.
     </p>
     <p>
      This option is like
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-source">
       <code class="option">
        --read-from-remote-source=BINLOG-DUMP-NON-GTIDS
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_result-file">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_result-file">
       <code class="option">
        --result-file=
        <em class="replaceable">
         <code>
          name
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -r
       <em class="replaceable">
        <code>
         name
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for result-file">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --result-file=name
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304117504">
     </a>
     <a class="indexterm" name="idm46045304116016">
     </a>
     <p>
      Without the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
       <code class="option">
        --raw
       </code>
      </a>
      option, this option indicates the file to which
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      writes text output. With
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
       <code class="option">
        --raw
       </code>
      </a>
      ,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      writes one binary output file
            for each log file transferred from the server, writing them
            by default in the current directory using the same names as
            the original log file. In this case, the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_result-file">
       <code class="option">
        --result-file
       </code>
      </a>
      option
            value is treated as a prefix that modifies output file
            names.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_require-row-format">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_require-row-format">
       <code class="option">
        --require-row-format
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for require-row-format">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --require-row-format
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           false
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304096112">
     </a>
     <a class="indexterm" name="idm46045304094608">
     </a>
     <p>
      Require row-based binary logging format for events. This
            option enforces row-based replication events for
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      output. The stream of events
            produced with this option would be accepted by a replication
            channel that is secured using the
      <code class="literal">
       REQUIRE_ROW_FORMAT
      </code>
      option of the
      <a class="link" href="change-replication-source-to.html" title="15.4.2.2 CHANGE REPLICATION SOURCE TO Statement">
       <code class="literal">
        CHANGE REPLICATION SOURCE TO
       </code>
      </a>
      statement.
      <a class="link" href="replication-options-binary-log.html#sysvar_binlog_format">
       <code class="literal">
        binlog_format=ROW
       </code>
      </a>
      must be
            set on the server where the binary log was written. When you
            specify this option,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      stops
            with an error message if it encounters any events that are
            disallowed under the
      <code class="literal">
       REQUIRE_ROW_FORMAT
      </code>
      restrictions, including
      <code class="literal">
       LOAD DATA INFILE
      </code>
      instructions, creating or dropping temporary tables,
      <code class="literal">
       INTVAR
      </code>
      ,
      <code class="literal">
       RAND
      </code>
      , or
      <code class="literal">
       USER_VAR
      </code>
      events, and non-row-based events
            within a DML transaction.
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      also prints a
      <code class="literal">
       SET
            @@session.require_row_format
      </code>
      statement at the
            start of its output to apply the restrictions when the
            output is executed, and does not print the
      <code class="literal">
       SET
            @@session.pseudo_thread_id
      </code>
      statement.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_rewrite-db">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_rewrite-db">
       <code class="option">
        --rewrite-db='
        <em class="replaceable">
         <code>
          from_name
         </code>
        </em>
        -&gt;
        <em class="replaceable">
         <code>
          to_name
         </code>
        </em>
        '
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for rewrite-db">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --rewrite-db='oldname-&gt;newname'
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           [none]
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304066800">
     </a>
     <a class="indexterm" name="idm46045304065312">
     </a>
     <p>
      When reading from a row-based or statement-based log,
            rewrite all occurrences of
      <em class="replaceable">
       <code>
        from_name
       </code>
      </em>
      to
      <em class="replaceable">
       <code>
        to_name
       </code>
      </em>
      . Rewriting is done on the
            rows, for row-based logs, as well as on the
      <a class="link" href="use.html" title="15.8.4 USE Statement">
       <code class="literal">
        USE
       </code>
      </a>
      clauses, for
            statement-based logs.
     </p>
     <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Warning
      </div>
      <p>
       Statements in which table names are qualified with
              database names are not rewritten to use the new name when
              using this option.
      </p>
     </div>
     <p>
      The rewrite rule employed as a value for this option is a
            string having the form
      <code class="literal">
       '
       <em class="replaceable">
        <code>
         from_name
        </code>
       </em>
       -&gt;
       <em class="replaceable">
        <code>
         to_name
        </code>
       </em>
       '
      </code>
      ,
            as shown previously, and for this reason must be enclosed by
            quotation marks.
     </p>
     <p>
      To employ multiple rewrite rules, specify the option
            multiple times, as shown here:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa36536909"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog <span class="token constant">--rewrite-db</span>=<span class="token atrule">'dbcurrent-&gt;dbold'</span> <span class="token constant">--rewrite-db</span>=<span class="token atrule">'dbtest-&gt;dbcurrent'</span> \
    binlog<span class="token punctuation">.</span>00001 &gt; /tmp/statements<span class="token punctuation">.</span>sql</code></pre>
     </div>
     <p>
      When used together with the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_database">
       <code class="option">
        --database
       </code>
      </a>
      option, the
      <code class="option">
       --rewrite-db
      </code>
      option is applied first; then
      <code class="option">
       --database
      </code>
      option is applied, using the
            rewritten database name. The order in which the options are
            provided makes no difference in this regard.
     </p>
     <p>
      This means that, for example, if
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      is started with
      <code class="option">
       --rewrite-db='mydb-&gt;yourdb'
            --database=yourdb
      </code>
      , then all updates to any tables
            in databases
      <code class="literal">
       mydb
      </code>
      and
      <code class="literal">
       yourdb
      </code>
      are included in the output. On the
            other hand, if it is started with
      <code class="option">
       --rewrite-db='mydb-&gt;yourdb'
            --database=mydb
      </code>
      , then
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      outputs no statements at all:
            since all updates to
      <code class="literal">
       mydb
      </code>
      are first
            rewritten as updates to
      <code class="literal">
       yourdb
      </code>
      before
            applying the
      <code class="option">
       --database
      </code>
      option, there
            remain no updates that match
      <code class="option">
       --database=mydb
      </code>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_server-id">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-id">
       <code class="option">
        --server-id=
        <em class="replaceable">
         <code>
          id
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for server-id">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --server-id=id
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304035600">
     </a>
     <a class="indexterm" name="idm46045304034112">
     </a>
     <p>
      Display only those events created by the server having the
            given server ID.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_server-id-bits">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-id-bits">
       <code class="option">
        --server-id-bits=
        <em class="replaceable">
         <code>
          N
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for server-id-bits">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --server-id-bits=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           32
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           7
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Maximum Value
         </th>
         <td>
          <code class="literal">
           32
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045304014864">
     </a>
     <a class="indexterm" name="idm46045304013376">
     </a>
     <p>
      Use only the first
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      bits of the
      <a class="link" href="replication-options.html#sysvar_server_id">
       <code class="literal">
        server_id
       </code>
      </a>
      to identify the
            server. If the binary log was written by a
      <a class="link" href="mysqld.html" title="6.3.1 mysqld — The MySQL Server">
       <span class="command">
        <strong>
         mysqld
        </strong>
       </span>
      </a>
      with server-id-bits set to less
            than 32 and user data stored in the most significant bit,
            running
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      with
      <code class="option">
       --server-id-bits
      </code>
      set to 32 enables this
            data to be seen.
     </p>
     <p>
      This option is supported only by the version of
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      supplied with the NDB Cluster
            distribution, or built with NDB Cluster support.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_server-public-key-path">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-public-key-path">
       <code class="option">
        --server-public-key-path=
        <em class="replaceable">
         <code>
          file_name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for server-public-key-path">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --server-public-key-path=file_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          File name
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303994720">
     </a>
     <a class="indexterm" name="idm46045303993216">
     </a>
     <p>
      The path name to a file in PEM format containing a
            client-side copy of the public key required by the server
            for RSA key pair-based password exchange. This option
            applies to clients that authenticate with the
      <code class="literal">
       sha256_password
      </code>
      (deprecated) or
      <code class="literal">
       caching_sha2_password
      </code>
      authentication
            plugin. This option is ignored for accounts that do not
            authenticate with one of those plugins. It is also ignored
            if RSA-based password exchange is not used, as is the case
            when the client connects to the server using a secure
            connection.
     </p>
     <p>
      If
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_server-public-key-path">
       <code class="option">
        --server-public-key-path=
        <em class="replaceable">
         <code>
          file_name
         </code>
        </em>
       </code>
      </a>
      is given and specifies a valid public key file, it takes
            precedence over
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_get-server-public-key">
       <code class="option">
        --get-server-public-key
       </code>
      </a>
      .
     </p>
     <p>
      For
      <code class="literal">
       sha256_password
      </code>
      (deprecated), this
            option applies only if MySQL was built using OpenSSL.
     </p>
     <p>
      For information about the
      <code class="literal">
       sha256_password
      </code>
      and
      <code class="literal">
       caching_sha2_password
      </code>
      plugins, see
      <a class="xref" href="sha256-pluggable-authentication.html" title="8.4.1.3 SHA-256 Pluggable Authentication">
       Section 8.4.1.3, “SHA-256 Pluggable Authentication”
      </a>
      , and
      <a class="xref" href="caching-sha2-pluggable-authentication.html" title="8.4.1.2 Caching SHA-2 Pluggable Authentication">
       Section 8.4.1.2, “Caching SHA-2 Pluggable Authentication”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_set-charset">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_set-charset">
       <code class="option">
        --set-charset=
        <em class="replaceable">
         <code>
          charset_name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for set-charset">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --set-charset=charset_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303971888">
     </a>
     <a class="indexterm" name="idm46045303970400">
     </a>
     <p>
      Add a
      <a class="link" href="set-names.html" title="15.7.6.3 SET NAMES Statement">
       <code class="literal">
        SET NAMES
        <em class="replaceable">
         <code>
          charset_name
         </code>
        </em>
       </code>
      </a>
      statement
            to the output to specify the character set to be used for
            processing log files.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_shared-memory-base-name">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_shared-memory-base-name">
       <code class="option">
        --shared-memory-base-name=
        <em class="replaceable">
         <code>
          name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for shared-memory-base-name">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --shared-memory-base-name=name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Platform Specific
         </th>
         <td>
          Windows
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303956720">
     </a>
     <a class="indexterm" name="idm46045303955216">
     </a>
     <p>
      On Windows, the shared-memory name to use for connections
            made using shared memory to a local server. The default
            value is
      <code class="literal">
       MYSQL
      </code>
      . The shared-memory name is
            case-sensitive.
     </p>
     <p>
      This option applies only if the server was started with the
      <a class="link" href="server-system-variables.html#sysvar_shared_memory">
       <code class="literal">
        shared_memory
       </code>
      </a>
      system
            variable enabled to support shared-memory connections.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_short-form">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_short-form">
       <code class="option">
        --short-form
       </code>
      </a>
      ,
      <code class="option">
       -s
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for short-form">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --short-form
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303942608">
     </a>
     <a class="indexterm" name="idm46045303941120">
     </a>
     <p>
      Display only the statements contained in the log, without
            any extra information or row-based events. This is for
            testing only, and should not be used in production systems.
            It is deprecated, and you should expect it to be removed in
            a future release.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_skip-gtids">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_skip-gtids">
       <code class="option">
        --skip-gtids[=(true|false)]
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for skip-gtids">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --skip-gtids[=true|false]
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           false
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303926672">
     </a>
     <a class="indexterm" name="idm46045303925184">
     </a>
     <p>
      Do not include the GTIDs from the binary log files in the
            output dump file. For example:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa23782039"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog <span class="token property">--skip-gtids</span> binlog<span class="token punctuation">.</span>000001 &gt;  /tmp/dump<span class="token punctuation">.</span>sql
mysql <span class="token property">-u</span> root <span class="token property">-p</span> <span class="token property">-e</span> <span class="token atrule">"source /tmp/dump.sql"</span></code></pre>
     </div>
     <p>
      You should not normally use this option in production or in
            recovery, except in the specific, and rare, scenarios where
            the GTIDs are actively unwanted. For example, an
            administrator might want to duplicate selected transactions
            (such as table definitions) from a deployment to another,
            unrelated, deployment that will not replicate to or from the
            original. In that scenario,
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_skip-gtids">
       <code class="option">
        --skip-gtids
       </code>
      </a>
      can be used to enable the administrator to apply the
            transactions as if they were new, and ensure that the
            deployments remain unrelated. However, you should only use
            this option if the inclusion of the GTIDs causes a known
            issue for your use case.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_socket">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_socket">
       <code class="option">
        --socket=
        <em class="replaceable">
         <code>
          path
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -S
       <em class="replaceable">
        <code>
         path
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for socket">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --socket={file_name|pipe_name}
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303909008">
     </a>
     <a class="indexterm" name="idm46045303907520">
     </a>
     <p>
      For connections to
      <code class="literal">
       localhost
      </code>
      , the Unix
            socket file to use, or, on Windows, the name of the named
            pipe to use.
     </p>
     <p>
      On Windows, this option applies only if the server was
            started with the
      <a class="link" href="server-system-variables.html#sysvar_named_pipe">
       <code class="literal">
        named_pipe
       </code>
      </a>
      system variable enabled to support named-pipe connections.
            In addition, the user making the connection must be a member
            of the Windows group specified by the
      <a class="link" href="server-system-variables.html#sysvar_named_pipe_full_access_group">
       <code class="literal">
        named_pipe_full_access_group
       </code>
      </a>
      system variable.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_ssl">
      </a>
      <code class="option">
       --ssl*
      </code>
     </p>
     <a class="indexterm" name="idm46045303900000">
     </a>
     <a class="indexterm" name="idm46045303898512">
     </a>
     <p>
      Options that begin with
      <code class="option">
       --ssl
      </code>
      specify
            whether to connect to the server using encryption and
            indicate where to find SSL keys and certificates. See
      <a class="xref" href="connection-options.html#encrypted-connection-options" title="Command Options for Encrypted Connections">
       Command Options for Encrypted Connections
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_ssl-fips-mode">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl-fips-mode">
       <code class="option">
        --ssl-fips-mode={OFF|ON|STRICT}
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for ssl-fips-mode">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --ssl-fips-mode={OFF|ON|STRICT}
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Deprecated
         </th>
         <td>
          Yes
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Enumeration
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           OFF
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Valid Values
         </th>
         <td>
          <p class="valid-value">
           <code class="literal">
            OFF
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            ON
           </code>
          </p>
          <p class="valid-value">
           <code class="literal">
            STRICT
           </code>
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303876432">
     </a>
     <a class="indexterm" name="idm46045303874944">
     </a>
     <p>
      Controls whether to enable FIPS mode on the client side. The
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl-fips-mode">
       <code class="option">
        --ssl-fips-mode
       </code>
      </a>
      option
            differs from other
      <code class="option">
       --ssl-
       <em class="replaceable">
        <code>
         xxx
        </code>
       </em>
      </code>
      options in that it is not used to establish encrypted
            connections, but rather to affect which cryptographic
            operations to permit. See
      <a class="xref" href="fips-mode.html" title="8.8 FIPS Support">
       Section 8.8, “FIPS Support”
      </a>
      .
     </p>
     <p>
      These
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl-fips-mode">
       <code class="option">
        --ssl-fips-mode
       </code>
      </a>
      values are permitted:
     </p>
     <div class="itemizedlist">
      <ul class="itemizedlist" style="list-style-type: circle; ">
       <li class="listitem">
        <p>
         <code class="literal">
          OFF
         </code>
         : Disable FIPS mode.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          ON
         </code>
         : Enable FIPS mode.
        </p>
       </li>
       <li class="listitem">
        <p>
         <code class="literal">
          STRICT
         </code>
         : Enable
         <span class="quote">
          “
          <span class="quote">
           strict
          </span>
          ”
         </span>
         FIPS mode.
        </p>
       </li>
      </ul>
     </div>
     <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
      <div class="admon-title">
       Note
      </div>
      <p>
       If the OpenSSL FIPS Object Module is not available, the
              only permitted value for
       <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl-fips-mode">
        <code class="option">
         --ssl-fips-mode
        </code>
       </a>
       is
       <code class="literal">
        OFF
       </code>
       . In this case, setting
       <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_ssl-fips-mode">
        <code class="option">
         --ssl-fips-mode
        </code>
       </a>
       to
       <code class="literal">
        ON
       </code>
       or
       <code class="literal">
        STRICT
       </code>
       causes
              the client to produce a warning at startup and to operate
              in non-FIPS mode.
      </p>
     </div>
     <p>
      This option is deprecated. Expect it to be removed in a
            future version of MySQL.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_start-datetime">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_start-datetime">
       <code class="option">
        --start-datetime=
        <em class="replaceable">
         <code>
          datetime
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for start-datetime">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --start-datetime=datetime
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Datetime
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303847984">
     </a>
     <a class="indexterm" name="idm46045303846496">
     </a>
     <p>
      Start reading the binary log at the first event having a
            timestamp equal to or later than the
      <em class="replaceable">
       <code>
        datetime
       </code>
      </em>
      argument. The
      <em class="replaceable">
       <code>
        datetime
       </code>
      </em>
      value is relative to the
            local time zone on the machine where you run
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      . The value should be in a
            format accepted for the
      <a class="link" href="datetime.html" title="13.2.2 The DATE, DATETIME, and TIMESTAMP Types">
       <code class="literal">
        DATETIME
       </code>
      </a>
      or
      <a class="link" href="datetime.html" title="13.2.2 The DATE, DATETIME, and TIMESTAMP Types">
       <code class="literal">
        TIMESTAMP
       </code>
      </a>
      data types. For
            example:
     </p>
     <div class="copytoclipboard-wrapper">
      <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa36461082"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog <span class="token constant">--start-datetime</span>=<span class="token atrule">"2005-12-25 11:25:56"</span> binlog<span class="token punctuation">.</span>000003</code></pre>
     </div>
     <p>
      This option is useful for point-in-time recovery. See
      <a class="xref" href="point-in-time-recovery.html" title="9.5 Point-in-Time (Incremental) Recovery">
       Section 9.5, “Point-in-Time (Incremental) Recovery”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_start-position">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_start-position">
       <code class="option">
        --start-position=
        <em class="replaceable">
         <code>
          N
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -j
       <em class="replaceable">
        <code>
         N
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for start-position">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --start-position=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303826848">
     </a>
     <a class="indexterm" name="idm46045303825360">
     </a>
     <p>
      Start decoding the binary log at the log position
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      , including in the output any
            events that begin at position
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      or after. The position is a byte point in the log file, not
            an event counter; it needs to point to the starting position
            of an event to generate useful output. This option applies
            to the first log file named on the command line.
     </p>
     <p>
      The maximum value supported for this option is
            18446744073709551616 (2
      <sup>
       64
      </sup>
      -1),
            unless
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
       <code class="option">
        --read-from-remote-server
       </code>
      </a>
      or
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-source">
       <code class="option">
        --read-from-remote-source
       </code>
      </a>
      is also used, in which case the maximum is 4294967295.
     </p>
     <p>
      This option is useful for point-in-time recovery. See
      <a class="xref" href="point-in-time-recovery.html" title="9.5 Point-in-Time (Incremental) Recovery">
       Section 9.5, “Point-in-Time (Incremental) Recovery”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_stop-datetime">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-datetime">
       <code class="option">
        --stop-datetime=
        <em class="replaceable">
         <code>
          datetime
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for stop-datetime">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --stop-datetime=datetime
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303810032">
     </a>
     <a class="indexterm" name="idm46045303808544">
     </a>
     <p>
      Stop reading the binary log at the first event having a
            timestamp equal to or later than the
      <em class="replaceable">
       <code>
        datetime
       </code>
      </em>
      argument. See the
            description of the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_start-datetime">
       <code class="option">
        --start-datetime
       </code>
      </a>
      option
            for information about the
      <em class="replaceable">
       <code>
        datetime
       </code>
      </em>
      value.
     </p>
     <p>
      This option is useful for point-in-time recovery. See
      <a class="xref" href="point-in-time-recovery.html" title="9.5 Point-in-Time (Incremental) Recovery">
       Section 9.5, “Point-in-Time (Incremental) Recovery”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_stop-never">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never">
       <code class="option">
        --stop-never
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for stop-never">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --stop-never
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Boolean
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           FALSE
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303791248">
     </a>
     <a class="indexterm" name="idm46045303789760">
     </a>
     <p>
      This option is used with
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
       <code class="option">
        --read-from-remote-server
       </code>
      </a>
      .
            It tells
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      to remain connected
            to the server. Otherwise
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      exits when the last log file has been transferred from the
            server.
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never">
       <code class="option">
        --stop-never
       </code>
      </a>
      implies
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_to-last-log">
       <code class="option">
        --to-last-log
       </code>
      </a>
      ,
            so only the first log file to transfer need be named on the
            command line.
     </p>
     <p>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never">
       <code class="option">
        --stop-never
       </code>
      </a>
      is commonly
            used with
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
       <code class="option">
        --raw
       </code>
      </a>
      to make
            a live binary log backup, but also can be used without
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_raw">
       <code class="option">
        --raw
       </code>
      </a>
      to maintain a
            continuous text display of log events as the server
            generates them.
     </p>
     <p>
      With
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never">
       <code class="option">
        --stop-never
       </code>
      </a>
      , by
            default,
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      reports a server ID
            of 1 when it connects to the server. Use
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_connection-server-id">
       <code class="option">
        --connection-server-id
       </code>
      </a>
      to explicitly specify an alternative ID to report. It can be
            used to avoid a conflict with the ID of a replica server or
            another
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      process. See
      <a class="xref" href="mysqlbinlog-server-id.html" title="6.6.9.4 Specifying the mysqlbinlog Server ID">
       Section 6.6.9.4, “Specifying the mysqlbinlog Server ID”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_stop-never-slave-server-id">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-never-slave-server-id">
       <code class="option">
        --stop-never-slave-server-id=
        <em class="replaceable">
         <code>
          id
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for stop-never-slave-server-id">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --stop-never-slave-server-id=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <code class="literal">
           65535
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Minimum Value
         </th>
         <td>
          <code class="literal">
           1
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303757856">
     </a>
     <a class="indexterm" name="idm46045303756352">
     </a>
     <p>
      This option is deprecated; expect it to be removed in a
            future release. Use the
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_connection-server-id">
       <code class="option">
        --connection-server-id
       </code>
      </a>
      option instead to specify a server ID for
      <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
       <span class="command">
        <strong>
         mysqlbinlog
        </strong>
       </span>
      </a>
      to report.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_stop-position">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-position">
       <code class="option">
        --stop-position=
        <em class="replaceable">
         <code>
          N
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for stop-position">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --stop-position=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Numeric
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303742048">
     </a>
     <a class="indexterm" name="idm46045303740560">
     </a>
     <p>
      Stop decoding the binary log at the log position
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      , excluding from the output any
            events that begin at position
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      or after. The position is a byte point in the log file, not
            an event counter; it needs to point to a spot after the
            starting position of the last event you want to include in
            the output. The event starting before position
      <em class="replaceable">
       <code>
        N
       </code>
      </em>
      and finishing at or after the
            position is the last event to be processed. This option
            applies to the last log file named on the command line.
     </p>
     <p>
      This option is useful for point-in-time recovery. See
      <a class="xref" href="point-in-time-recovery.html" title="9.5 Point-in-Time (Incremental) Recovery">
       Section 9.5, “Point-in-Time (Incremental) Recovery”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_tls-ciphersuites">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_tls-ciphersuites">
       <code class="option">
        --tls-ciphersuites=
        <em class="replaceable">
         <code>
          ciphersuite_list
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for tls-ciphersuites">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --tls-ciphersuites=ciphersuite_list
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303725696">
     </a>
     <a class="indexterm" name="idm46045303724208">
     </a>
     <p>
      The permissible ciphersuites for encrypted connections that
            use TLSv1.3. The value is a list of one or more
            colon-separated ciphersuite names. The ciphersuites that can
            be named for this option depend on the SSL library used to
            compile MySQL. For details, see
      <a class="xref" href="encrypted-connection-protocols-ciphers.html" title="8.3.2 Encrypted Connection TLS Protocols and Ciphers">
       Section 8.3.2, “Encrypted Connection TLS Protocols and Ciphers”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_tls-sni-servername">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_tls-sni-servername">
       <code class="option">
        --tls-sni-servername=
        <em class="replaceable">
         <code>
          server_name
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for tls-sni-servername">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --tls-sni-servername=server_name
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303711280">
     </a>
     <a class="indexterm" name="idm46045303709776">
     </a>
     <p>
      When specified, the name is passed to the
      <code class="literal">
       libmysqlclient
      </code>
      C API library using the
      <code class="literal">
       MYSQL_OPT_TLS_SNI_SERVERNAME
      </code>
      option of
      <a class="ulink" href="/doc/c-api/8.4/en/mysql-options.html" target="_top">
       <code class="literal">
        mysql_options()
       </code>
      </a>
      . The server
            name is not case-sensitive. To show which server name the
            client specified for the current session, if any, check the
      <a class="link" href="server-status-variables.html#statvar_Tls_sni_server_name">
       <code class="literal">
        Tls_sni_server_name
       </code>
      </a>
      status
            variable.
     </p>
     <p>
      Server Name Indication (SNI) is an extension to the TLS
            protocol (OpenSSL must be compiled using TLS extensions for
            this option to function). The MySQL implementation of SNI
            represents the client-side only.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_tls-version">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_tls-version">
       <code class="option">
        --tls-version=
        <em class="replaceable">
         <code>
          protocol_list
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for tls-version">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --tls-version=protocol_list
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
        <tr>
         <th>
          Default Value
         </th>
         <td>
          <p class="valid-value">
           <code class="literal">
            TLSv1,TLSv1.1,TLSv1.2,TLSv1.3
           </code>
           (OpenSSL 1.1.1 or higher)
          </p>
          <p class="valid-value">
           <code class="literal">
            TLSv1,TLSv1.1,TLSv1.2
           </code>
           (otherwise)
          </p>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303688896">
     </a>
     <a class="indexterm" name="idm46045303687408">
     </a>
     <p>
      The permissible TLS protocols for encrypted connections. The
            value is a list of one or more comma-separated protocol
            names. The protocols that can be named for this option
            depend on the SSL library used to compile MySQL. For
            details, see
      <a class="xref" href="encrypted-connection-protocols-ciphers.html" title="8.3.2 Encrypted Connection TLS Protocols and Ciphers">
       Section 8.3.2, “Encrypted Connection TLS Protocols and Ciphers”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_to-last-log">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_to-last-log">
       <code class="option">
        --to-last-log
       </code>
      </a>
      ,
      <code class="option">
       -t
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for to-last-log">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --to-last-log
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303676448">
     </a>
     <a class="indexterm" name="idm46045303674960">
     </a>
     <p>
      Do not stop at the end of the requested binary log from a
            MySQL server, but rather continue printing until the end of
            the last binary log. If you send the output to the same
            MySQL server, this may lead to an endless loop. This option
            requires
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_read-from-remote-server">
       <code class="option">
        --read-from-remote-server
       </code>
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_user">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_user">
       <code class="option">
        --user=
        <em class="replaceable">
         <code>
          user_name
         </code>
        </em>
       </code>
      </a>
      ,
      <code class="option">
       -u
       <em class="replaceable">
        <code>
         user_name
        </code>
       </em>
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for user">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --user=user_name,
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          String
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303661040">
     </a>
     <a class="indexterm" name="idm46045303659552">
     </a>
     <p>
      The user name of the MySQL account to use when connecting to
            a remote server.
     </p>
     <p>
      If you are using the
      <code class="literal">
       Rewriter
      </code>
      plugin, you
            should grant this user the
      <a class="link" href="privileges-provided.html#priv_skip-query-rewrite">
       <code class="literal">
        SKIP_QUERY_REWRITE
       </code>
      </a>
      privilege.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_verbose">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verbose">
       <code class="option">
        --verbose
       </code>
      </a>
      ,
      <code class="option">
       -v
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for verbose">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --verbose
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303647024">
     </a>
     <a class="indexterm" name="idm46045303645536">
     </a>
     <p>
      Reconstruct row events and display them as commented SQL
            statements, with table partition information where
            applicable. If this option is given twice (by passing in
            either "-vv" or "--verbose --verbose"), the output includes
            comments to indicate column data types and some metadata,
            and informational log events such as row query log events if
            the
      <a class="link" href="replication-options-binary-log.html#sysvar_binlog_rows_query_log_events">
       <code class="literal">
        binlog_rows_query_log_events
       </code>
      </a>
      system variable is set to
      <code class="literal">
       TRUE
      </code>
      .
     </p>
     <p>
      For examples that show the effect of
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_base64-output">
       <code class="option">
        --base64-output
       </code>
      </a>
      and
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verbose">
       <code class="option">
        --verbose
       </code>
      </a>
      on row event
            output, see
      <a class="xref" href="mysqlbinlog-row-events.html" title="6.6.9.2 mysqlbinlog Row Event Display">
       Section 6.6.9.2, “mysqlbinlog Row Event Display”
      </a>
      .
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_verify-binlog-checksum">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_verify-binlog-checksum">
       <code class="option">
        --verify-binlog-checksum
       </code>
      </a>
      ,
      <code class="option">
       -c
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for verify-binlog-checksum">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --verify-binlog-checksum
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303629696">
     </a>
     <a class="indexterm" name="idm46045303628192">
     </a>
     <p>
      Verify checksums in binary log files.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_version">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_version">
       <code class="option">
        --version
       </code>
      </a>
      ,
      <code class="option">
       -V
      </code>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for version">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --version
          </code>
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303618192">
     </a>
     <a class="indexterm" name="idm46045303616704">
     </a>
     <p>
      Display version information and exit.
     </p>
    </li>
    <li class="listitem">
     <p>
      <a name="option_mysqlbinlog_zstd-compression-level">
      </a>
      <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_zstd-compression-level">
       <code class="option">
        --zstd-compression-level=
        <em class="replaceable">
         <code>
          level
         </code>
        </em>
       </code>
      </a>
     </p>
     <div class="informaltable">
      <table frame="box" rules="all" summary="Properties for zstd-compression-level">
       <colgroup>
        <col style="width: 30%"/>
        <col style="width: 70%"/>
       </colgroup>
       <tbody>
        <tr>
         <th>
          Command-Line Format
         </th>
         <td>
          <code class="literal">
           --zstd-compression-level=#
          </code>
         </td>
        </tr>
        <tr>
         <th>
          Type
         </th>
         <td>
          Integer
         </td>
        </tr>
       </tbody>
      </table>
     </div>
     <a class="indexterm" name="idm46045303604656">
     </a>
     <a class="indexterm" name="idm46045303603152">
     </a>
     <p>
      The compression level to use for connections to the server
            that use the
      <code class="literal">
       zstd
      </code>
      compression algorithm.
            The permitted levels are from 1 to 22, with larger values
            indicating increasing levels of compression. The default
      <code class="literal">
       zstd
      </code>
      compression level is 3. The
            compression level setting has no effect on connections that
            do not use
      <code class="literal">
       zstd
      </code>
      compression.
     </p>
     <p>
      For more information, see
      <a class="xref" href="connection-compression-control.html" title="6.2.8 Connection Compression Control">
       Section 6.2.8, “Connection Compression Control”
      </a>
      .
     </p>
    </li>
   </ul>
  </div>
  <p>
   You can pipe the output of
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   into
        the
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   client to execute the events
        contained in the binary log. This technique is used to recover
        from an unexpected exit when you have an old backup (see
   <a class="xref" href="point-in-time-recovery.html" title="9.5 Point-in-Time (Incremental) Recovery">
    Section 9.5, “Point-in-Time (Incremental) Recovery”
   </a>
   ). For example:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa49954988"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog binlog<span class="token punctuation">.</span>000001 | mysql <span class="token property">-u</span> root <span class="token property">-p</span></code></pre>
  </div>
  <p>
   Or:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa73286005"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog binlog<span class="token punctuation">.</span><span class="token punctuation">[</span>0-9<span class="token punctuation">]</span>* | mysql <span class="token property">-u</span> root <span class="token property">-p</span></code></pre>
  </div>
  <p>
   If the statements produced by
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   may
        contain
   <a class="link" href="blob.html" title="13.3.4 The BLOB and TEXT Types">
    <code class="literal">
     BLOB
    </code>
   </a>
   values, these may
        cause problems when
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   processes them. In
        this case, invoke
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   with the
   <a class="link" href="mysql-command-options.html#option_mysql_binary-mode">
    <code class="option">
     --binary-mode
    </code>
   </a>
   option.
  </p>
  <p>
   You can also redirect the output of
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   to a text file instead, if you
        need to modify the statement log first (for example, to remove
        statements that you do not want to execute for some reason).
        After editing the file, execute the statements that it contains
        by using it as input to the
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   program:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa48229751"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog binlog<span class="token punctuation">.</span>000001 &gt; tmpfile
<span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span> <em class="replaceable">edit tmpfile</em> <span class="token punctuation">.</span><span class="token punctuation">.</span><span class="token punctuation">.</span>
mysql <span class="token property">-u</span> root <span class="token property">-p</span> &lt; tmpfile</code></pre>
  </div>
  <p>
   When
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   is invoked with the
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_start-position">
    <code class="option">
     --start-position
    </code>
   </a>
   option, it
        displays only those events with an offset in the binary log
        greater than or equal to a given position (the given position
        must match the start of one event). It also has options to stop
        and start when it sees an event with a given date and time. This
        enables you to perform point-in-time recovery using the
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_stop-datetime">
    <code class="option">
     --stop-datetime
    </code>
   </a>
   option (to
        be able to say, for example,
   <span class="quote">
    “
    <span class="quote">
     roll forward my databases to
        how they were today at 10:30 a.m.
    </span>
    ”
   </span>
   ).
  </p>
  <p>
   <b>
    Processing multiple files.
   </b>
   If you have more than one binary log to execute on the MySQL
          server, the safe method is to process them all using a single
          connection to the server. Here is an example that demonstrates
          what may be
   <span class="emphasis">
    <em>
     unsafe
    </em>
   </span>
   :
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa55750589"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog binlog<span class="token punctuation">.</span>000001 | mysql <span class="token property">-u</span> root <span class="token property">-p</span> <span class="token comment" spellcheck="true"># DANGER!!</span>
mysqlbinlog binlog<span class="token punctuation">.</span>000002 | mysql <span class="token property">-u</span> root <span class="token property">-p</span> <span class="token comment" spellcheck="true"># DANGER!!</span></code></pre>
  </div>
  <p>
   Processing binary logs this way using multiple connections to
        the server causes problems if the first log file contains a
   <a class="link" href="create-table.html" title="15.1.20 CREATE TABLE Statement">
    <code class="literal">
     CREATE TEMPORARY
        TABLE
    </code>
   </a>
   statement and the second log contains a
        statement that uses the temporary table. When the first
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   process terminates, the server drops
        the temporary table. When the second
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   process attempts to use the table, the server reports
   <span class="quote">
    “
    <span class="quote">
     unknown table.
    </span>
    ”
   </span>
  </p>
  <p>
   To avoid problems like this, use a
   <span class="emphasis">
    <em>
     single
    </em>
   </span>
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   process to execute the contents of all
        binary logs that you want to process. Here is one way to do so:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa56341165"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog binlog<span class="token punctuation">.</span>000001 binlog<span class="token punctuation">.</span>000002 | mysql <span class="token property">-u</span> root <span class="token property">-p</span></code></pre>
  </div>
  <p>
   Another approach is to write all the logs to a single file and
        then process the file:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting language-terminal"><div class="docs-select-all right" id="sa59553034"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">mysqlbinlog binlog<span class="token punctuation">.</span>000001 &gt;  /tmp/statements<span class="token punctuation">.</span>sql
mysqlbinlog binlog<span class="token punctuation">.</span>000002 &gt;&gt; /tmp/statements<span class="token punctuation">.</span>sql
mysql <span class="token property">-u</span> root <span class="token property">-p</span> <span class="token property">-e</span> <span class="token atrule">"source /tmp/statements.sql"</span></code></pre>
  </div>
  <p>
   You can also supply multiple binary log files to
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   as streamed input using a shell
        pipe. An archive of compressed binary log files can be
        decompressed and provided directly to
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   . In this example,
   <code class="filename">
    binlog-files_1.gz
   </code>
   contains multiple binary
        log files for processing. The pipeline extracts the contents of
   <code class="filename">
    binlog-files_1.gz
   </code>
   , pipes the binary log
        files to
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   as standard input, and
        pipes the output of
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   into the
   <a class="link" href="mysql.html" title="6.5.1 mysql — The MySQL Command-Line Client">
    <span class="command">
     <strong>
      mysql
     </strong>
    </span>
   </a>
   client for execution:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa12662044"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">gzip <span class="token property">-cd</span> binlog-files_1<span class="token punctuation">.</span>gz | <span class="token punctuation">.</span>/mysqlbinlog - | <span class="token punctuation">.</span>/mysql <span class="token property">-uroot</span>  <span class="token property">-p</span></code></pre>
  </div>
  <p>
   You can specify more than one archive file, for example:
  </p>
  <div class="copytoclipboard-wrapper">
   <pre class="programlisting one-line language-terminal"><div class="docs-select-all right" id="sa74917401"><div class="copy-help left">Press ⌘+C to copy</div> <div class="right"><button class="clipboard-btn" title="Copy to Clipboard"><span class="icon-clipboard"></span></button></div></div><code class="language-terminal">gzip <span class="token property">-cd</span> binlog-files_1<span class="token punctuation">.</span>gz binlog-files_2<span class="token punctuation">.</span>gz | <span class="token punctuation">.</span>/mysqlbinlog - | <span class="token punctuation">.</span>/mysql <span class="token property">-uroot</span>  <span class="token property">-p</span></code></pre>
  </div>
  <p>
   For streamed input, do not use
   <code class="literal">
    --stop-position
   </code>
   , because
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   cannot identify the last log file
        to apply this option.
  </p>
  <p>
   <b>
    LOAD DATA operations.
   </b>
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   can produce output that
          reproduces a
   <a class="link" href="load-data.html" title="15.2.9 LOAD DATA Statement">
    <code class="literal">
     LOAD DATA
    </code>
   </a>
   operation without the original data file.
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   copies the data to a temporary
          file and writes a
   <a class="link" href="load-data.html" title="15.2.9 LOAD DATA Statement">
    <code class="literal">
     LOAD DATA
          LOCAL
    </code>
   </a>
   statement that refers to the file. The default
          location of the directory where these files are written is
          system-specific. To specify a directory explicitly, use the
   <a class="link" href="mysqlbinlog.html#option_mysqlbinlog_local-load">
    <code class="option">
     --local-load
    </code>
   </a>
   option.
  </p>
  <p>
   Because
   <a class="link" href="mysqlbinlog.html" title="6.6.9 mysqlbinlog — Utility for Processing Binary Log Files">
    <span class="command">
     <strong>
      mysqlbinlog
     </strong>
    </span>
   </a>
   converts
   <a class="link" href="load-data.html" title="15.2.9 LOAD DATA Statement">
    <code class="literal">
     LOAD DATA
    </code>
   </a>
   statements to
   <a class="link" href="load-data.html" title="15.2.9 LOAD DATA Statement">
    <code class="literal">
     LOAD DATA
        LOCAL
    </code>
   </a>
   statements (that is, it adds
   <code class="literal">
    LOCAL
   </code>
   ), both the client and the server that
        you use to process the statements must be configured with the
   <code class="literal">
    LOCAL
   </code>
   capability enabled. See
   <a class="xref" href="load-data-local-security.html" title="8.1.6 Security Considerations for LOAD DATA LOCAL">
    Section 8.1.6, “Security Considerations for LOAD DATA LOCAL”
   </a>
   .
  </p>
  <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
   <div class="admon-title">
    Warning
   </div>
   <p>
    The temporary files created for
    <a class="link" href="load-data.html" title="15.2.9 LOAD DATA Statement">
     <code class="literal">
      LOAD DATA
          LOCAL
     </code>
    </a>
    statements are
    <span class="emphasis">
     <em>
      not
     </em>
    </span>
    automatically deleted because they are needed until you
          actually execute those statements. You should delete the
          temporary files yourself after you no longer need the
          statement log. The files can be found in the temporary file
          directory and have names like
    <em class="replaceable">
     <code>
      original_file_name-#-#
     </code>
    </em>
    .
   </p>
  </div>
 </div>
 <br/>
</div>
