<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="reserved-accounts">
      </a>
      8.2.9 Reserved Accounts
     </h3>
    </div>
   </div>
  </div>
  <a class="indexterm" name="idm46045249447568">
  </a>
  <a class="indexterm" name="idm46045249446496">
  </a>
  <a class="indexterm" name="idm46045249445008">
  </a>
  <p>
   One part of the MySQL installation process is data directory
      initialization (see
   <a class="xref" href="data-directory-initialization.html" title="2.9.1 Initializing the Data Directory">
    Section 2.9.1, “Initializing the Data Directory”
   </a>
   ). During data
      directory initialization, MySQL creates user accounts that should
      be considered reserved:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      <code class="literal">
       'root'@'localhost
      </code>
      : Used for administrative
          purposes. This account has all privileges, is a system
          account, and can perform any operation.
     </p>
     <p>
      Strictly speaking, this account name is not reserved, in the
          sense that some installations rename the
      <code class="literal">
       root
      </code>
      account to something else to avoid
          exposing a highly privileged account with a well-known name.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       'mysql.sys'@'localhost'
      </code>
      : Used as the
      <code class="literal">
       DEFINER
      </code>
      for
      <a class="link" href="sys-schema.html" title="Chapter 30 MySQL sys Schema">
       <code class="literal">
        sys
       </code>
      </a>
      schema objects. Use of the
      <code class="literal">
       mysql.sys
      </code>
      account avoids problems that
          occur if a DBA renames or removes the
      <code class="literal">
       root
      </code>
      account. This account is locked so that it cannot be used for
          client connections.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       'mysql.session'@'localhost'
      </code>
      : Used
          internally by plugins to access the server. This account is
          locked so that it cannot be used for client connections. The
          account is a system account.
     </p>
    </li>
    <li class="listitem">
     <p>
      <code class="literal">
       'mysql.infoschema'@'localhost'
      </code>
      : Used as the
      <code class="literal">
       DEFINER
      </code>
      for
      <a class="link" href="information-schema.html" title="Chapter 28 INFORMATION_SCHEMA Tables">
       <code class="literal">
        INFORMATION_SCHEMA
       </code>
      </a>
      views. Use of
          the
      <code class="literal">
       mysql.infoschema
      </code>
      account avoids
          problems that occur if a DBA renames or removes the root
          account. This account is locked so that it cannot be used for
          client connections.
     </p>
    </li>
   </ul>
  </div>
 </div>
 <br/>
</div>
