linkend="manage-ag-overview"/>.
    </para>
   </glossdef>
  </glossentry>

  <glossentry id="glossary-sql-standard">
   <glossterm>SQL standard</glossterm>
   <glossdef>
    <para>
     A series of documents that define the <acronym>SQL</acronym> language.
    </para>
   </glossdef>
  </glossentry>

  <glossentry>
   <glossterm>Standby (server)</glossterm>
   <glosssee otherterm="glossary-replica" />
  </glossentry>

  <glossentry id="glossary-startup-process">
   <glossterm>Startup process</glossterm>
   <glossdef>
    <para>
     An <glossterm linkend="glossary-auxiliary-proc">auxiliary process</glossterm>
     that replays WAL during crash recovery and in a
     <glossterm linkend="glossary-replication">physical replica</glossterm>.
    </para>
    <para>
     (The name is historical: the startup process was named before
     replication was implemented; the name refers to its task as it
     relates to the server startup following a crash.)
    </para>
   </glossdef>
  </glossentry>

  <glossentry id="glossary-superuser">
   <glossterm>Superuser</glossterm>
   <glossdef>
    <para>
     As used in this documentation, it is a synonym for
     <glossterm linkend="glossary-database-superuser">database superuser</glossterm>.
    </para>
   </glossdef>
  </glossentry>

  <glossentry id="glossary-system-catalog">
   <glossterm>System catalog</glossterm>
   <glossdef>
    <para>
     A collection of <glossterm linkend="glossary-table">tables</glossterm>
     which describe the structure of all
     <glossterm linkend="glossary-sql-object">SQL objects</glossterm>
     of the instance.
     The system catalog resides in the schema <literal>pg_catalog</literal>.
     These tables contain data in internal representation and are
     not typically considered useful for user examination;
     a number of user-friendlier <glossterm linkend="glossary-view">views</glossterm>,
     also in schema <literal>pg_catalog</literal>, offer more convenient access to
     some of that information, while additional tables and views
     exist in schema <literal>information_schema</literal>
     (see <xref linkend="information-schema" />) that expose some
     of the same and additional information as mandated by the
     <glossterm linkend="glossary-sql-standard">SQL standard</glossterm>.
    </para>
    <para>
      For more information, see
      <xref linkend="ddl-schemas"/>.
    </para>
   </glossdef>
  </glossentry>

  <glossentry id="glossary-table">
   <glossterm>Table</glossterm>
   <glossdef>
    <para>
     A collection of <glossterm linkend="glossary-tuple">tuples</glossterm> having
     a common data structure (the same number of
     <glossterm linkend="glossary-attribute">attributes</glossterm>, in the same
     order, having the same name and type per position).
     A table is the most common form of
     <glossterm linkend="glossary-relation">relation</glossterm> in
     <productname>PostgreSQL</productname>.
    </para>
    <para>
     For more information, see
     <xref linkend="sql-createtable"/>.
    </para>
   </glossdef>
  </glossentry>

  <glossentry id="glossary-tablespace">
   <glossterm>Tablespace</glossterm>
   <glossdef>
    <para>
     A named location on the server file system.
     All <glossterm linkend="glossary-sql-object">SQL objects</glossterm>
     which require storage beyond their definition in the
     <glossterm linkend="glossary-system-catalog">system catalog</glossterm>
     must belong to a single tablespace.
     Initially, a database cluster contains a single usable tablespace which is
     used as the default for all SQL objects, called <literal>pg_default</literal>.
    </para>
    <para>
     For more information, see
     <xref linkend="manage-ag-tablespaces"/>.
    </para>
   </glossdef>
  </glossentry>

  <glossentry id="glossary-temporary-table">
   <glossterm>Temporary table</glossterm>
   <glossdef>
    <para>
     <glossterm linkend="glossary-table">Tables</glossterm> that exist either