text:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic
  PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<topic xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/" id="topic1" xml:lang="en"
  ditaarch:DITAArchVersion="1.1"
  domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
  class="- topic/topic ">
  <title id="ie179298" class="- topic/title ">The gp_toolkit
    Administrative Schema</title>

Greenplum Database provides an administrative schema called <codeph
        class="+ topic/ph pr-d/codeph ">gp_toolkit</codeph> that you
      can use to query the system catalogs, log files, and operating environment for system status
      information. The <codeph class="+ topic/ph pr-d/codeph ">gp_toolkit</codeph> schema contains a number of views that you can access using SQL commands.
      The <codeph class="+ topic/ph pr-d/codeph ">gp_toolkit</codeph>
      schema is accessible to all database users, although some objects may require superuser
      permissions. For convenience, you may want to add the <codeph class="+ topic/ph pr-d/codeph "
          >gp_toolkit</codeph> schema to your schema search path. For
      example:

    <codeblock>=> ALTER ROLE myrole SET search_path TO myschema,gp_toolkit;</codeblock>

This documentation describes the most useful views in <codeph class="+ topic/ph pr-d/codeph "
          >gp_toolkit</codeph>. You may notice other objects (views,
      functions, and external tables) within the <codeph class="+ topic/ph pr-d/codeph ">gp_toolkit</codeph> schema that are not described in this
      documentation (these are supporting objects to the views described in this section).

    <note type="warning" class="- topic/note ">Do not change database objects in the gp_toolkit schema. Do not create database objects in the schema.
      Changes to objects in the schema might affect the accuracy of administrative information
      returned by schema objects. <ph>Any changes made in the gp_toolkit schema are lost when the database is backed up and then
        restored with the <codeph class="+ topic/ph pr-d/codeph ">gpcrondump</codeph> and <codeph
          class="+ topic/ph pr-d/codeph ">gpdbrestore</codeph> utilities. </ph></note>

These are the categories for views in the <codeph>gp_toolkit</codeph>
      schema.

  <topic id="topic2" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Checking for Tables that Need Routine Maintenance</title>

The following views can help identify tables that need routine table maintenance (<codeph
          class="+ topic/ph pr-d/codeph ">VACUUM</codeph> and/or <codeph
          class="+ topic/ph pr-d/codeph ">ANALYZE</codeph>).

          <xref href="#topic3" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic4" type="topic" format="dita" class="- topic/xref "/>

The <codeph class="+ topic/ph pr-d/codeph ">VACUUM</codeph> or <codeph
          class="+ topic/ph pr-d/codeph ">VACUUM FULL</codeph> command reclaims disk space occupied
        by deleted or obsolete rows. Because of the MVCC transaction concurrency model used in
          Greenplum Database, data rows that are deleted or updated still occupy
        physical space on disk even though they are not visible to any new transactions. Expired
        rows increase table size on disk and eventually slow down scans of the table.

The <codeph class="+ topic/ph pr-d/codeph ">ANALYZE</codeph> command collects column-level
        statistics needed by the query optimizer. Greenplum Database uses a cost-based
        query optimizer that relies on database statistics. Accurate statistics allow the query
        optimizer to better estimate selectivity and the number of rows retrieved by a query
        operation in order to choose the most efficient query plan.

    <topic id="topic3" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie191889" class="- topic/title ">gp_bloat_diag</title>

This view shows regular heap-storage tables that have bloat (the actual number of pages
          on disk exceeds the expected number of pages given the table statistics). Tables that are
          bloated require a <codeph class="+ topic/ph pr-d/codeph ">VACUUM</codeph> or a <codeph
            class="+ topic/ph pr-d/codeph ">VACUUM FULL</codeph> in order to reclaim disk space
          occupied by deleted or obsolete rows. This view is accessible to all users, however
          non-superusers will only be able to see the tables that they have permission to
            access.<note> For diagnostic functions that return append-optimized table information,
            see <xref href="#topic8" format="dita"/>.</note>

          <title class="- topic/title ">gp_bloat_diag view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="267pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">bdirelid</entry>
                <entry colname="col2" class="- topic/entry ">Table object id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">bdinspname</entry>
                <entry colname="col2" class="- topic/entry ">Schema name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">bdirelname</entry>
                <entry colname="col2" class="- topic/entry ">Table name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">bdirelpages</entry>
                <entry colname="col2" class="- topic/entry ">Actual number of pages on disk.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">bdiexppages</entry>
                <entry colname="col2" class="- topic/entry ">Expected number of pages given the
                  table data.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">bdidiag</entry>
                <entry colname="col2" class="- topic/entry ">Bloat diagnostic message.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic4" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie194264" class="- topic/title ">gp_stats_missing</title>

This view shows tables that do not have statistics and therefore may require an <codeph
            class="+ topic/ph pr-d/codeph ">ANALYZE</codeph> be run on the table.

          <title class="- topic/title ">gp_stats_missing view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="268pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">smischema </entry>
                <entry colname="col2" class="- topic/entry ">Schema name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">smitable </entry>
                <entry colname="col2" class="- topic/entry ">Table name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">smisize </entry>
                <entry colname="col2" class="- topic/entry ">Does this table have statistics? False
                  if the table does not have row count and row sizing statistics recorded in the
                  system catalog, which may indicate that the table needs to be analyzed. This will
                  also be false if the table does not contain any rows. For example, the parent
                  tables of partitioned tables are always empty and will always return a false
                  result. </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">smicols </entry>
                <entry colname="col2" class="- topic/entry ">Number of columns in the table.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">smirecs </entry>
                <entry colname="col2" class="- topic/entry ">Number of rows in the table.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic5" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Checking for Locks</title>

When a transaction accesses a relation (such as a table), it acquires a lock. Depending on
        the type of lock acquired, subsequent transactions may have to wait before they can access
        the same relation. For more information on the types of locks, see "Managing Data" in the
          Greenplum Database Administrator Guide. Greenplum Database resource queues (used
        for workload management) also use locks to control the admission of queries into the
        system.

The <codeph class="+ topic/ph pr-d/codeph ">gp_locks_*</codeph> family of views can help
        diagnose queries and sessions that are waiting to access an object due to a lock.

          <xref href="#topic6" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic7" type="topic" format="dita" class="- topic/xref "/>

    <topic id="topic6" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie192116" class="- topic/title ">gp_locks_on_relation</title>

This view shows any locks currently being held on a relation, and the associated session
          information about the query associated with the lock. For more information on the types of
          locks, see "Managing Data" in the Greenplum Database Administrator Guide. This view
          is accessible to all users, however non-superusers will only be able to see the locks for
          relations that they have permission to access.

          <title class="- topic/title ">gp_locks_on_relation view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="111pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorlocktype</entry>
                <entry colname="col2" class="- topic/entry ">Type of the lockable object: <codeph
                    class="+ topic/ph pr-d/codeph ">relation</codeph>, <codeph
                    class="+ topic/ph pr-d/codeph ">extend</codeph>, <codeph
                    class="+ topic/ph pr-d/codeph ">page</codeph>, <codeph
                    class="+ topic/ph pr-d/codeph ">tuple</codeph>, <codeph
                    class="+ topic/ph pr-d/codeph ">transactionid</codeph>, <codeph
                    class="+ topic/ph pr-d/codeph ">object</codeph>, <codeph
                    class="+ topic/ph pr-d/codeph ">userlock</codeph>, <codeph
                    class="+ topic/ph pr-d/codeph ">resource queue</codeph>, or <codeph
                    class="+ topic/ph pr-d/codeph ">advisory</codeph></entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lordatabase</entry>
                <entry colname="col2" class="- topic/entry ">Object ID of the database in which the
                  object exists, zero if the object is a shared object.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorrelname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the relation.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorrelation</entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the relation.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lortransaction</entry>
                <entry colname="col2" class="- topic/entry ">The transaction ID that is affected by
                  the lock.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorpid</entry>
                <entry colname="col2" class="- topic/entry ">Process ID of the server process
                  holding or awaiting this lock. NULL if the lock is held by a prepared
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lormode</entry>
                <entry colname="col2" class="- topic/entry ">Name of the lock mode held or desired
                  by this process.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorgranted</entry>
                <entry colname="col2" class="- topic/entry ">Displays whether the lock is granted
                  (true) or not granted (false).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorcurrentquery</entry>
                <entry colname="col2" class="- topic/entry ">The current query in the
                  session.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic7" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie179843" class="- topic/title ">gp_locks_on_resqueue </title>

This view shows any locks currently being held on a resource queue, and the associated
          session information about the query associated with the lock. This view is accessible to
          all users, however non-superusers will only be able to see the locks associated with their
          own sessions.

          <title class="- topic/title ">gp_locks_on_resqueue view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="110pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorusename</entry>
                <entry colname="col2" class="- topic/entry ">Name of the user executing the
                  session.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorrsqname</entry>
                <entry colname="col2" class="- topic/entry ">The resource queue name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorlocktype</entry>
                <entry colname="col2" class="- topic/entry ">Type of the lockable object: <codeph
                    class="+ topic/ph pr-d/codeph ">resource queue</codeph></entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorobjid</entry>
                <entry colname="col2" class="- topic/entry ">The ID of the locked
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lortransaction</entry>
                <entry colname="col2" class="- topic/entry ">The ID of the transaction that is
                  affected by the lock.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorpid</entry>
                <entry colname="col2" class="- topic/entry ">The process ID of the transaction that
                  is affected by the lock.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lormode</entry>
                <entry colname="col2" class="- topic/entry ">The name of the lock mode held or
                  desired by this process.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorgranted</entry>
                <entry colname="col2" class="- topic/entry ">Displays whether the lock is granted
                  (true) or not granted (false).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">lorwaiting</entry>
                <entry colname="col2" class="- topic/entry ">Displays whether or not the session is
                  waiting.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic8" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Checking Append-Optimized Tables</title>

The <codeph>gp_toolkit</codeph> schema includes a set of diagnostic functions you can use
        to investigate the state of append-optimized tables.

When an append-optimized table (or column-oriented append-optimized table) is created,
        another table is implicitly created, containing metadata about the current state of the
        table. The metadata includes information such as the number of records in each of the
        table's segments.

Append-optimized tables may have non-visible rows—rows that have been updated or deleted,
        but remain in storage until the table is compacted using <codeph
          class="+ topic/ph pr-d/codeph ">VACUUM</codeph>. The hidden rows are tracked using an
        auxiliary visibility map table, or visimap.

The following functions let you access the metadata for append-optimized and
        column-oriented tables and view non-visible rows. Some of the functions have two versions:
        one that takes the <codeph class="+ topic/ph pr-d/codeph ">oid</codeph> of the table, and
        one that takes the name of the table. The latter version has "_name" appended to the
        function name.

    <topic id="topic_ylp_gxw_yq">
      <title>__gp_aovisimap_compaction_info(oid)</title>

This function displays compaction information for an append-optimized table. The
          information is for the on-disk data files on Greenplum Database segments that store the
          table data. You can use the information to determine the data files that will be compacted
          by a <codeph>VACUUM</codeph> operation on an append-optimized table.

        <note>Until a <cmdname>VACUUM</cmdname> operation deletes the row from the data file,
          deleted or updated data rows occupy physical space on disk even though they are hidden to
          new transactions. The configuration parameter <codeph>gp_appendonly_compaction</codeph>
          controls the functionality of the <codeph>VACUUM</codeph> command.</note>

This table describes the <cmdname>__gp_aovisimap_compaction_info</cmdname> function
          output table.

          <title>__gp_aovisimap_compaction_info output table</title>
          <tgroup cols="2">
            <colspec colnum="1" colname="col1" colwidth="108pt"/>
            <colspec colnum="2" colname="col2" colwidth="266pt"/>

              <row>
                <entry>Column</entry>
                <entry>Description</entry>
              </row>

              <row>
                <entry>content</entry>
                <entry>Greenplum Database segment ID.</entry>
              </row>
              <row>
                <entry>datafile</entry>
                <entry>ID of the data file on the segment.</entry>
              </row>
              <row>
                <entry>compaction_possible</entry>
                <entry>The value is either <codeph>t</codeph> or <codeph>f</codeph>. The value
                    <codeph>t</codeph> indicates that the data in data file be compacted when a
                    <cmdname>VACUUM</cmdname> operation is performed.
The server configuration
                    parameter <codeph>gp_appendonly_compaction_threshold</codeph> affects this
                    value.
</entry>
              </row>
              <row>
                <entry>hidden_tupcount</entry>
                <entry>In the data file, the number of hidden (deleted or updated) rows. </entry>
              </row>
              <row>
                <entry>total_tupcount</entry>
                <entry>In the data file, the total number of rows. </entry>
              </row>
              <row>
                <entry>percent_hidden</entry>
                <entry>In the data file, the ratio (as a percentage) of hidden (deleted or updated)
                  rows to total rows. </entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic9" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title class="- topic/title ">__gp_aoseg_name('table_name')</title>

This function returns metadata information contained in the append-optimized table's
          on-disk segment file.

          <title class="- topic/title ">__gp_aoseg_name output table</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">segno</entry>
                <entry colname="col2" class="- topic/entry ">The file segment number. </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof</entry>
                <entry colname="col2" class="- topic/entry ">The effective end of file for this file
                  segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">tupcount</entry>
                <entry colname="col2" class="- topic/entry ">The total number of tuples in the
                  segment, including invisible tuples. </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">varblockcount</entry>
                <entry colname="col2" class="- topic/entry ">The total number of varblocks in the
                  file segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof_uncompressed</entry>
                <entry colname="col2" class="- topic/entry ">The end of file if the file segment
                  were uncompressed.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">modcount</entry>
                <entry colname="col2" class="- topic/entry ">The number of data modification
                  operations.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">state</entry>
                <entry colname="col2" class="- topic/entry ">The state of the file segment.
                  Indicates if the segment is active or ready to be dropped after compaction.
                </entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic10" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title class="- topic/title ">__gp_aoseg_history(oid)</title>

This function returns metadata information contained in the append-optimized table's
          on-disk segment file. It displays all different versions (heap tuples) of the aoseg meta
          information. The data is complex, but users with a deep understanding of the system may
          find it usefulfor debugging.

The input argument is the oid of the append-optimized table.

Call __gp_aoseg_history_name('table_name') to get the same result with the table name as
          an argument.

          <title class="- topic/title ">__gp_aoseg_history output table</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="115pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="260pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_tid</entry>
                <entry colname="col2" class="- topic/entry ">The id of the tuple.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmin</entry>
                <entry colname="col2" class="- topic/entry ">The id of the earliest
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmin_status</entry>
                <entry colname="col2" class="- topic/entry ">Status of the gp_xmin
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmin_commit_</entry>
                <entry colname="col2" class="- topic/entry ">The commit distribution id of the
                  gp_xmin transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmax</entry>
                <entry colname="col2" class="- topic/entry ">The id of the latest
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmax_status</entry>
                <entry colname="col2" class="- topic/entry ">The status of the latest
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmax_commit_</entry>
                <entry colname="col2" class="- topic/entry ">The commit distribution id of the
                  gp_xmax transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_command_id</entry>
                <entry colname="col2" class="- topic/entry ">The id of the query command. </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_infomask</entry>
                <entry colname="col2" class="- topic/entry ">A bitmap containing state
                  information.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_update_tid</entry>
                <entry colname="col2" class="- topic/entry ">The ID of the newer tuple if the row is
                  updated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_visibility</entry>
                <entry colname="col2" class="- topic/entry ">The tuple visibility status.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">segno</entry>
                <entry colname="col2" class="- topic/entry ">The number of the segment in the
                  segment file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">tupcount</entry>
                <entry colname="col2" class="- topic/entry ">The number of tuples, including hidden
                  tuples.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof</entry>
                <entry colname="col2" class="- topic/entry ">The effective end of file for the
                  segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof_uncompressed</entry>
                <entry colname="col2" class="- topic/entry ">The end of file for the segment if data
                  were uncompressed.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">modcount</entry>
                <entry colname="col2" class="- topic/entry ">A count of data modifications.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">state</entry>
                <entry colname="col2" class="- topic/entry ">The status of the segment.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic11" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title class="- topic/title ">__gp_aocsseg(oid)</title>

This function returns metadata information contained in a column-oriented
          append-optimized table's on-disk segment file, excluding non-visible rows. Each row
          describes a segment for a column in the table.

The input argument is the oid of a column-oriented append-optimized table. Call as
          __gp_aocsseg_name('table_name') to get the same result with the table name as an
          argument.

          <title class="- topic/title ">__gp_aocsseg(oid) output table</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_tid</entry>
                <entry colname="col2" class="- topic/entry ">The table id. </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">segno</entry>
                <entry colname="col2" class="- topic/entry ">The segment number.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">column_num</entry>
                <entry colname="col2" class="- topic/entry ">The column number.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">physical_segno</entry>
                <entry colname="col2" class="- topic/entry ">The number of the segment in the
                  segment file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">tupcount</entry>
                <entry colname="col2" class="- topic/entry ">The number of rows in the segment,
                  excluding hidden tuples.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof</entry>
                <entry colname="col2" class="- topic/entry ">The effective end of file for the
                  segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof_uncompressed</entry>
                <entry colname="col2" class="- topic/entry ">The end of file for the segment if the
                  data were uncompressed.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">modcount</entry>
                <entry colname="col2" class="- topic/entry ">A count of data modification operations
                  for the segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">state</entry>
                <entry colname="col2" class="- topic/entry ">The status of the segment.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic12" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title class="- topic/title ">__gp_aocsseg_history(oid)</title>

This function returns metadata information contained in a column-oriented
          append-optimized table's on-disk segment file. Each row describes a segment for a column
          in the table. The data is complex, but users with a deep understanding of the system may
          find it useful for debugging.

The input argument is the oid of a column-oriented append-optimized table. Call as
          __gp_aocsseg_history_name('table_name') to get the same result with the table name as
          argument.

          <title class="- topic/title ">__gp_aocsseg_history output table</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_tid</entry>
                <entry colname="col2" class="- topic/entry ">The oid of the tuple.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmin</entry>
                <entry colname="col2" class="- topic/entry ">The earliest transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmin_status</entry>
                <entry colname="col2" class="- topic/entry ">The status of the gp_xmin
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmin_</entry>
                <entry colname="col2" class="- topic/entry ">Text representation of gp_xmin.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmax</entry>
                <entry colname="col2" class="- topic/entry ">The latest transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmax_status</entry>
                <entry colname="col2" class="- topic/entry ">The status of the gp_xmax
                  transaction.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_xmax_</entry>
                <entry colname="col2" class="- topic/entry ">Text representation of gp_max.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_command_id</entry>
                <entry colname="col2" class="- topic/entry ">ID of the command operating on the
                  tuple.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_infomask</entry>
                <entry colname="col2" class="- topic/entry ">A bitmap containing state
                  information.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_update_tid</entry>
                <entry colname="col2" class="- topic/entry ">The ID of the newer tuple if the row is
                  updated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">gp_visibility</entry>
                <entry colname="col2" class="- topic/entry ">The tuple visibility status.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">segno</entry>
                <entry colname="col2" class="- topic/entry ">The segment number in the segment
                  file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">column_num</entry>
                <entry colname="col2" class="- topic/entry ">The column number.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">physical_segno</entry>
                <entry colname="col2" class="- topic/entry ">The segment containing data for the
                  column.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">tupcount</entry>
                <entry colname="col2" class="- topic/entry ">The total number of tuples in the
                  segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof</entry>
                <entry colname="col2" class="- topic/entry ">The effective end of file for the
                  segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">eof_uncompressed</entry>
                <entry colname="col2" class="- topic/entry ">The end of file for the segment if the
                  data were uncompressed.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">modcount</entry>
                <entry colname="col2" class="- topic/entry ">A count of the data modification
                  operations.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">state</entry>
                <entry colname="col2" class="- topic/entry ">The state of the segment.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic13" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title class="- topic/title ">__gp_aovisimap(oid)</title>

This function returns the tuple id, the segment file, and the row number of each
          non-visible tuple according to the visibility map.

The input argument is the oid of an append-optimized table.

Use __gp_aovisimap_name('table_name') to get the same result with the table name as
          argument.

          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">tid</entry>
                <entry colname="col2" class="- topic/entry ">The tuple id. </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">segno</entry>
                <entry colname="col2" class="- topic/entry ">The number of the segment file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">row_num</entry>
                <entry colname="col2" class="- topic/entry ">The row number of a row that has been
                  deleted or updated.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic14" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title class="- topic/title ">__gp_aovisimap_hidden_info(oid)</title>

This function returns the numbers of hidden and visible tuples in the segment files for
          an append-optimized table.

The input argument is the oid of the append-optimized table.

Call __gp_aovisimap_hidden_info_name('table_name') to get the same result with a table
          name argument.

          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">segno</entry>
                <entry colname="col2" class="- topic/entry ">The number of the segment file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">hidden_tupcount</entry>
                <entry colname="col2" class="- topic/entry ">The number of hidden tuples in the
                  segment file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">total_tupcount</entry>
                <entry colname="col2" class="- topic/entry ">The total number of tuples in the
                  segment file. </entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic15" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title class="- topic/title ">__gp_aovisimap_entry(oid) </title>

This function returns information about each visibility map entry for the table.

The input argument is the oid of an append-optimized table.

Call __gp_aovisimap_entry_name('table_name') to get the same result with a table name
          argument.

          <title class="- topic/title ">__gp_aovisimap_entry output table</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="108pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">segno</entry>
                <entry colname="col2" class="- topic/entry ">Segment number of the visibility map
                  entry. </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">first_row_num</entry>
                <entry colname="col2" class="- topic/entry ">The first row number of the
                  entry.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">hidden_tupcount</entry>
                <entry colname="col2" class="- topic/entry ">The number of hidden tuples in the
                  entry.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">bitmap</entry>
                <entry colname="col2" class="- topic/entry ">A text representation of the visibility
                  bitmap.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic16" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Viewing Greenplum Database Server Log Files</title>

Each component of a Greenplum Database system (master, standby master,
        primary segments, and mirror segments) keeps its own server log files. The <codeph
          class="+ topic/ph pr-d/codeph ">gp_log_*</codeph> family of
        views allows you to issue SQL queries against the server log files to find particular
        entries of interest. The use of these views require superuser permissions.

          <xref href="#topic17" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic18" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic19" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic20" type="topic" format="dita" class="- topic/xref "/>

    <topic id="topic17" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie192312" class="- topic/title ">gp_log_command_timings</title>

This view uses an external table to read the log files on the master and report the
          execution time of SQL commands executed in a database session. The use of this view
          requires superuser permissions.

          <title class="- topic/title ">gp_log_command_timings
            view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="262pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsession </entry>
                <entry colname="col2" class="- topic/entry ">The session identifier (prefixed with
                  "con").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcmdcount </entry>
                <entry colname="col2" class="- topic/entry ">The command number within a session
                  (prefixed with "cmd").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdatabase </entry>
                <entry colname="col2" class="- topic/entry ">The name of the database.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loguser </entry>
                <entry colname="col2" class="- topic/entry ">The name of the database user.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logpid </entry>
                <entry colname="col2" class="- topic/entry ">The process id (prefixed with
                  "p").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logtimemin </entry>
                <entry colname="col2" class="- topic/entry ">The time of the first log message for
                  this command.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logtimemax </entry>
                <entry colname="col2" class="- topic/entry ">The time of the last log message for
                  this command.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logduration </entry>
                <entry colname="col2" class="- topic/entry ">Statement duration from start to end
                  time. </entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic18" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie173484" class="- topic/title ">gp_log_database</title>

This view uses an external table to read the server log files of the entire Greenplum system (master, segments, and mirrors) and lists log
          entries associated with the current database. Associated log entries can be identified by
          the session id (logsession) and command id (logcmdcount). The use of this view requires
          superuser permissions.

          <title class="- topic/title ">gp_log_database view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="263pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logtime </entry>
                <entry colname="col2" class="- topic/entry ">The timestamp of the log
                  message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loguser </entry>
                <entry colname="col2" class="- topic/entry ">The name of the database user.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdatabase </entry>
                <entry colname="col2" class="- topic/entry ">The name of the database.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logpid </entry>
                <entry colname="col2" class="- topic/entry ">The associated process id (prefixed
                  with "p").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logthread </entry>
                <entry colname="col2" class="- topic/entry ">The associated thread count (prefixed
                  with "th").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loghost </entry>
                <entry colname="col2" class="- topic/entry ">The segment or master host
                  name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logport </entry>
                <entry colname="col2" class="- topic/entry ">The segment or master port.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsessiontime </entry>
                <entry colname="col2" class="- topic/entry ">Time session connection was
                  opened.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logtransaction </entry>
                <entry colname="col2" class="- topic/entry ">Global transaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsession </entry>
                <entry colname="col2" class="- topic/entry ">The session identifier (prefixed with
                  "con").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcmdcount </entry>
                <entry colname="col2" class="- topic/entry ">The command number within a session
                  (prefixed with "cmd").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsegment </entry>
                <entry colname="col2" class="- topic/entry ">The segment content identifier
                  (prefixed with "seg" for primary or "mir" for mirror. The master always has a
                  content id of -1).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logslice </entry>
                <entry colname="col2" class="- topic/entry ">The slice id (portion of the query plan
                  being executed).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdistxact </entry>
                <entry colname="col2" class="- topic/entry ">Distributed transaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loglocalxact </entry>
                <entry colname="col2" class="- topic/entry ">Local transaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsubxact </entry>
                <entry colname="col2" class="- topic/entry ">Subtransaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logseverity </entry>
                <entry colname="col2" class="- topic/entry ">LOG, ERROR, FATAL, PANIC, DEBUG1 or
                  DEBUG2.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logstate </entry>
                <entry colname="col2" class="- topic/entry ">SQL state code associated with the log
                  message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logmessage </entry>
                <entry colname="col2" class="- topic/entry ">Log or error message text.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdetail </entry>
                <entry colname="col2" class="- topic/entry ">Detail message text associated with an
                  error message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loghint </entry>
                <entry colname="col2" class="- topic/entry ">Hint message text associated with an
                  error message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logquery </entry>
                <entry colname="col2" class="- topic/entry ">The internally-generated query
                  text.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logquerypos </entry>
                <entry colname="col2" class="- topic/entry ">The cursor index into the
                  internally-generated query text.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcontext </entry>
                <entry colname="col2" class="- topic/entry ">The context in which this message gets
                  generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdebug </entry>
                <entry colname="col2" class="- topic/entry ">Query string with full detail for
                  debugging.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcursorpos </entry>
                <entry colname="col2" class="- topic/entry ">The cursor index into the query
                  string.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logfunction </entry>
                <entry colname="col2" class="- topic/entry ">The function in which this message is
                  generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logfile </entry>
                <entry colname="col2" class="- topic/entry ">The log file in which this message is
                  generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logline </entry>
                <entry colname="col2" class="- topic/entry ">The line in the log file in which this
                  message is generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logstack</entry>
                <entry colname="col2" class="- topic/entry ">Full text of the stack trace associated
                  with this message.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic19" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie191863" class="- topic/title ">gp_log_master_concise</title>

This view uses an external table to read a subset of the log fields from the master log
          file. The use of this view requires superuser permissions.

          <title class="- topic/title ">gp_log_master_concise
            view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="113pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="263pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logtime </entry>
                <entry colname="col2" class="- topic/entry ">The timestamp of the log
                  message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdatabase </entry>
                <entry colname="col2" class="- topic/entry ">The name of the database.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsession </entry>
                <entry colname="col2" class="- topic/entry ">The session identifier (prefixed with
                  "con").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcmdcount </entry>
                <entry colname="col2" class="- topic/entry ">The command number within a session
                  (prefixed with "cmd").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logmessage </entry>
                <entry colname="col2" class="- topic/entry ">Log or error message text.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic20" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie173472" class="- topic/title ">gp_log_system</title>

This view uses an external table to read the server log files of the entire Greenplum system (master, segments, and mirrors) and lists all log
          entries. Associated log entries can be identified by the session id (logsession) and
          command id (logcmdcount). The use of this view requires superuser permissions.

          <title class="- topic/title ">gp_log_system view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="112pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="265pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logtime </entry>
                <entry colname="col2" class="- topic/entry ">The timestamp of the log
                  message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loguser </entry>
                <entry colname="col2" class="- topic/entry ">The name of the database user.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdatabase </entry>
                <entry colname="col2" class="- topic/entry ">The name of the database.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logpid </entry>
                <entry colname="col2" class="- topic/entry ">The associated process id (prefixed
                  with "p").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logthread </entry>
                <entry colname="col2" class="- topic/entry ">The associated thread count (prefixed
                  with "th").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loghost </entry>
                <entry colname="col2" class="- topic/entry ">The segment or master host
                  name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logport </entry>
                <entry colname="col2" class="- topic/entry ">The segment or master port.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsessiontime </entry>
                <entry colname="col2" class="- topic/entry ">Time session connection was
                  opened.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logtransaction </entry>
                <entry colname="col2" class="- topic/entry ">Global transaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsession </entry>
                <entry colname="col2" class="- topic/entry ">The session identifier (prefixed with
                  "con").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcmdcount </entry>
                <entry colname="col2" class="- topic/entry ">The command number within a session
                  (prefixed with "cmd").</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsegment </entry>
                <entry colname="col2" class="- topic/entry ">The segment content identifier
                  (prefixed with "seg" for primary or "mir" for mirror. The master always has a
                  content id of -1).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logslice </entry>
                <entry colname="col2" class="- topic/entry ">The slice id (portion of the query plan
                  being executed).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdistxact </entry>
                <entry colname="col2" class="- topic/entry ">Distributed transaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loglocalxact </entry>
                <entry colname="col2" class="- topic/entry ">Local transaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logsubxact </entry>
                <entry colname="col2" class="- topic/entry ">Subtransaction id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logseverity </entry>
                <entry colname="col2" class="- topic/entry ">LOG, ERROR, FATAL, PANIC, DEBUG1 or
                  DEBUG2.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logstate </entry>
                <entry colname="col2" class="- topic/entry ">SQL state code associated with the log
                  message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logmessage </entry>
                <entry colname="col2" class="- topic/entry ">Log or error message text.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdetail </entry>
                <entry colname="col2" class="- topic/entry ">Detail message text associated with an
                  error message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">loghint </entry>
                <entry colname="col2" class="- topic/entry ">Hint message text associated with an
                  error message.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logquery </entry>
                <entry colname="col2" class="- topic/entry ">The internally-generated query
                  text.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logquerypos </entry>
                <entry colname="col2" class="- topic/entry ">The cursor index into the
                  internally-generated query text.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcontext </entry>
                <entry colname="col2" class="- topic/entry ">The context in which this message gets
                  generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logdebug </entry>
                <entry colname="col2" class="- topic/entry ">Query string with full detail for
                  debugging.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logcursorpos </entry>
                <entry colname="col2" class="- topic/entry ">The cursor index into the query
                  string.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logfunction </entry>
                <entry colname="col2" class="- topic/entry ">The function in which this message is
                  generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logfile </entry>
                <entry colname="col2" class="- topic/entry ">The log file in which this message is
                  generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logline </entry>
                <entry colname="col2" class="- topic/entry ">The line in the log file in which this
                  message is generated.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">logstack </entry>
                <entry colname="col2" class="- topic/entry ">Full text of the stack trace associated
                  with this message.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic21" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Checking Server Configuration Files</title>

Each component of a Greenplum Database system (master, standby master, primary segments,
        and mirror segments) has its own server configuration file (<codeph
          class="+ topic/ph pr-d/codeph ">postgresql.conf</codeph>). The following <codeph
          class="+ topic/ph pr-d/codeph ">gp_toolkit</codeph> objects can be used to check parameter
        settings across all primary <codeph class="+ topic/ph pr-d/codeph ">postgresql.conf</codeph>
        files in the system:

          <xref href="#topic22" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic23" type="topic" format="dita" class="- topic/xref "/>

    <topic id="topic22" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie192965" class="- topic/title ">gp_param_setting('parameter_name')</title>

This function takes the name of a server configuration parameter and returns the <codeph
            class="+ topic/ph pr-d/codeph ">postgresql.conf</codeph> value for the master and each
          active segment. This function is accessible to all users.

          <title class="- topic/title ">gp_param_setting('parameter_name') function</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="115pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="262pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">paramsegment</entry>
                <entry colname="col2" class="- topic/entry ">The segment content id (only active
                  segments are shown). The master content id is always -1.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">paramname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the parameter.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">paramvalue</entry>
                <entry colname="col2" class="- topic/entry ">The value of the parameter.</entry>
              </row>

          </tgroup>

          <title class="- topic/title ">Example: </title>
          <codeblock>SELECT * FROM gp_param_setting('max_connections');</codeblock>

    </topic>
    <topic id="topic23" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie192963" class="- topic/title ">gp_param_settings_seg_value_diffs </title>

Server configuration parameters that are classified as local parameters (meaning each segment gets the parameter value from its own
            <codeph class="+ topic/ph pr-d/codeph ">postgresql.conf</codeph> file), should be set
          identically on all segments. This view shows local parameter settings that are
          inconsistent. Parameters that are supposed to have different values (such as <codeph
            class="+ topic/ph pr-d/codeph ">port</codeph>) are not included. This view is accessible
          to all users.

          <title class="- topic/title ">gp_param_settings_seg_value_diffs view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="115pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="262pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">psdname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the parameter.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">psdvalue</entry>
                <entry colname="col2" class="- topic/entry ">The value of the parameter.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">psdcount</entry>
                <entry colname="col2" class="- topic/entry ">The number of segments that have this
                  value.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic24" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Checking for Failed Segments</title>

The <xref href="#topic25" type="topic" format="dita" class="- topic/xref "/> view can be
        used to check for down segments.

    <topic id="topic25" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie193108" class="- topic/title ">gp_pgdatabase_invalid </title>

This view shows information about segments that are marked as down in the system catalog.
          This view is accessible to all users.

          <title class="- topic/title ">gp_pgdatabase_invalid view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="87pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="289pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">pgdbidbid</entry>
                <entry colname="col2" class="- topic/entry ">The segment dbid. Every segment has a
                  unique dbid.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">pgdbiisprimary</entry>
                <entry colname="col2" class="- topic/entry ">Is the segment currently acting as the
                  primary (active) segment? (t or f)</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">pgdbicontent</entry>
                <entry colname="col2" class="- topic/entry ">The content id of this segment. A
                  primary and mirror will have the same content id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">pgdbivalid</entry>
                <entry colname="col2" class="- topic/entry ">Is this segment up and valid? (t or
                  f)</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">pgdbidefinedprimary</entry>
                <entry colname="col2" class="- topic/entry ">Was this segment assigned the role of
                  primary at system initialization time? (t or f)</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic26" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Checking Resource Queue Activity and Status</title>

The purpose of resource queues is to limit the number of active queries in the system at
        any given time in order to avoid exhausting system resources such as memory, CPU, and disk
        I/O. All database users are assigned to a resource queue, and every statement submitted by a
        user is first evaluated against the resource queue limits before it can run. The <codeph
          class="+ topic/ph pr-d/codeph ">gp_resq_*</codeph> family of views can be used to check
        the status of statements currently submitted to the system through their respective resource
        queue. Note that statements issued by superusers are exempt from resource queuing.

          <xref href="#topic27" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic28" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic29" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic30" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic31" type="topic" format="dita" class="- topic/xref "/>

    <topic id="topic27" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie193152" class="- topic/title ">gp_resq_activity</title>

For the resource queues that have active workload, this view shows one row for each
          active statement submitted through a resource queue. This view is accessible to all
          users.

          <title class="- topic/title ">gp_resq_activity view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="85pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="291pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqprocpid </entry>
                <entry colname="col2" class="- topic/entry ">Process ID assigned to this statement
                  (on the master).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqrole </entry>
                <entry colname="col2" class="- topic/entry ">User name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqoid </entry>
                <entry colname="col2" class="- topic/entry ">Resource queue object id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqname </entry>
                <entry colname="col2" class="- topic/entry ">Resource queue name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqstart </entry>
                <entry colname="col2" class="- topic/entry ">Time statement was issued to the
                  system.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqstatus </entry>
                <entry colname="col2" class="- topic/entry ">Status of statement: running, waiting
                  or cancelled.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic28" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie173460" class="- topic/title ">gp_resq_activity_by_queue</title>

For the resource queues that have active workload, this view shows a summary of queue
          activity. This view is accessible to all users.

          <title class="- topic/title ">gp_resq_activity_by_queue Column </title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="109pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="266pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqoid </entry>
                <entry colname="col2" class="- topic/entry ">Resource queue object id.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqname </entry>
                <entry colname="col2" class="- topic/entry ">Resource queue name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqlast </entry>
                <entry colname="col2" class="- topic/entry ">Time of the last statement issued to
                  the queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqstatus </entry>
                <entry colname="col2" class="- topic/entry ">Status of last statement: running,
                  waiting or cancelled.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">resqtotal </entry>
                <entry colname="col2" class="- topic/entry ">Total statements in this queue.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic29" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie180197" class="- topic/title ">gp_resq_priority_statement</title>

This view shows the resource queue priority, session ID, and other information for all
          statements currently running in the Greenplum Database system. This view is accessible to
          all users.

          <title class="- topic/title ">gp_resq_priority_statement view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="109pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="267pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rqpdatname </entry>
                <entry colname="col2" class="- topic/entry ">The database name that the session is
                  connected to.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rqpusename </entry>
                <entry colname="col2" class="- topic/entry ">The user who issued the
                  statement.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rqpsession </entry>
                <entry colname="col2" class="- topic/entry ">The session ID.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rqpcommand </entry>
                <entry colname="col2" class="- topic/entry ">The number of the statement within this
                  session (the command id and session id uniquely identify a statement). </entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rqppriority </entry>
                <entry colname="col2" class="- topic/entry ">The resource queue priority for this
                  statement (MAX, HIGH, MEDIUM, LOW).</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rqpweight </entry>
                <entry colname="col2" class="- topic/entry ">An integer value associated with the
                  priority of this statement.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rqpquery </entry>
                <entry colname="col2" class="- topic/entry ">The query text of the
                  statement.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic30" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie196226" class="- topic/title ">gp_resq_role</title>

This view shows the resource queues associated with a role. This view is accessible to
          all users.

          <title class="- topic/title ">gp_resq_role view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="110pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="267pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rrrolname</entry>
                <entry colname="col2" class="- topic/entry ">Role (user) name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rrrsqname </entry>
                <entry colname="col2" class="- topic/entry ">The resource queue name assigned to
                  this role. If a role has not been explicitly assigned to a resource queue, it will
                  be in the default resource queue (pg_default).
                </entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic31" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie196285" class="- topic/title ">gp_resqueue_status</title>

This view allows administrators to see status and activity for a workload management
          resource queue. It shows how many queries are waiting to run and how many queries are
          currently active in the system from a particular resource queue.

          <title class="- topic/title ">gp_resqueue_status view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="178pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="198pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">queueid</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The ID of the resource queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqname</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The name of the resource queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqcountlimit</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The active query threshold of the
                  resource queue. A value of -1 means no limit.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqcountvalue</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The number of active query slots
                  currently being used in the resource queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqcostlimit</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The query cost threshold of the
                  resource queue. A value of -1 means no limit.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqcostvalue</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The total cost of all statements
                  currently in the resource queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqmemorylimit</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The memory limit for the resource
                  queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqmemoryvalue</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The total memory used by all statements
                  currently in the resource queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqwaiters</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The number of statements currently
                  waiting in the resource queue.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">rsqholders</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">The number of statements currently
                  running on the system from this resource queue.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/" id="topic32" xml:lang="en"
    ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Checking Query Disk Spill Space Usage</title>

The gp_workfile_* views
        show information about all the queries that are currently using disk spill space. Greenplum Database creates work files on disk if it does not have sufficient memory
        to execute the query in memory. This information can be used for troubleshooting and tuning
        queries. The information in the views can also be used to specify the values for the
          Greenplum Database configuration parameters <codeph
          class="+ topic/ph pr-d/codeph ">gp_workfile_limit_per_query</codeph> and <codeph class="+ topic/ph pr-d/codeph ">gp_workfile_limit_per_segment</codeph>.

          <xref href="#topic33" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic34" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic35" type="topic" format="dita" class="- topic/xref "/>

    <topic id="topic33" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie202615" class="- topic/title ">gp_workfile_entries</title>

This view contains one row for each operator using disk space for workfiles on a segment
          at the current time. The view is accessible to all users, however non-superusers only to
          see information for the databases that they have permission to access.

          <title class="- topic/title ">gp_workfile_entries</title>
          <tgroup cols="4" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="131pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="97pt" class="- topic/colspec "/>
            <colspec colnum="3" colname="col3" colwidth="82pt" class="- topic/colspec "/>
            <colspec colnum="4" colname="col4" colwidth="138pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Type</entry>
                <entry colname="col3" class="- topic/entry ">References</entry>
                <entry colname="col4" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">command_cnt</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">integer</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Command ID of the query.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">content</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">smallint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The content identifier for a segment
                  instance.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">current_query</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">text</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Current query that the process is
                  running.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">datname</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">name</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Greenplum
                  database name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">directory</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">text</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Path to the work file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">optype</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">text</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The query operator type that created
                  the work file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">procpid </codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">integer</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Process ID of the server
                  process.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">sess_id</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">integer</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Session ID.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">size </codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">bigint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The size of the work file in
                  bytes.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">numfiles</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">bigint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The number of files created.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">slice</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">smallint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The query plan slice. The portion of
                  the query plan that is being executed.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">state</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">text</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The state of the query that created the
                  work file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">usename</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">name</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Role name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">workmem</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">integer</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The amount of memory allocated to the
                  operator in KB.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic34" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie202748" class="- topic/title ">gp_workfile_usage_per_query</title>

This view contains one row for each query using disk space for workfiles on a segment at
          the current time. The view is accessible to all users, however non-superusers only to see
          information for the databases that they have permission to access.

          <title class="- topic/title ">gp_workfile_usage_per_query</title>
          <tgroup cols="4" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="131pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="97pt" class="- topic/colspec "/>
            <colspec colnum="3" colname="col3" colwidth="82pt" class="- topic/colspec "/>
            <colspec colnum="4" colname="col4" colwidth="138pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Type</entry>
                <entry colname="col3" class="- topic/entry ">References</entry>
                <entry colname="col4" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">command_cnt</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">integer</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Command ID of the query.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">content</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">smallint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The content identifier for a segment
                  instance.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">current_query</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">text</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Current query that the process is
                  running.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">datname</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">name</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Greenplum
                  database name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">procpid </codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">integer</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Process ID of the server
                  process.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">sess_id</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">integer</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Session ID.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">size</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">bigint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The size of the work file in
                  bytes.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">numfiles</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">bigint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The number of files created.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">state</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">text</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The state of the query that created the
                  work file.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">usename</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">name</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">Role name.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic35" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie202849" class="- topic/title ">gp_workfile_usage_per_segment</title>

This view contains one row for each segment. Each row displays the total amount of disk
          space used for workfiles on the segment at the current time. The view is accessible to all
          users, however non-superusers only to see information for the databases that they have
          permission to access.

          <title class="- topic/title ">gp_workfile_usage_per_segment</title>
          <tgroup cols="4" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="131pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="97pt" class="- topic/colspec "/>
            <colspec colnum="3" colname="col3" colwidth="82pt" class="- topic/colspec "/>
            <colspec colnum="4" colname="col4" colwidth="138pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Type</entry>
                <entry colname="col3" class="- topic/entry ">References</entry>
                <entry colname="col4" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">content</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">smallint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The content identifier for a segment
                  instance.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">size</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">bigint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The total size of the work files on a
                  segment.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">
                  <codeph class="+ topic/ph pr-d/codeph ">numfiles</codeph>
                </entry>
                <entry colname="col2" class="- topic/entry ">bigint</entry>
                <entry colname="col3" class="- topic/entry "/>
                <entry colname="col4" class="- topic/entry ">The number of files created.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic36" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title class="- topic/title ">Viewing Users and Groups (Roles)</title>

It is frequently convenient to group users (roles) together to ease management of object
        privileges: that way, privileges can be granted to, or revoked from, a group as a whole. In
        Greenplum Database this is done by creating a role that represents the group, and then
        granting membership in the group role to individual user roles.

The <xref href="#topic37" type="topic" format="dita" class="- topic/xref "/> view can be
        used to see all of the roles in the system, and their assigned members (if the role is also
        a group role).

    <topic id="topic37" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie192504" class="- topic/title ">gp_roles_assigned </title>

This view shows all of the roles in the system, and their assigned members (if the role
          is also a group role). This view is accessible to all users.

          <title class="- topic/title ">gp_roles_assigned view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="261pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">raroleid</entry>
                <entry colname="col2" class="- topic/entry ">The role object ID. If this role has
                  members (users), it is considered a group
                  role.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">rarolename</entry>
                <entry colname="col2" class="- topic/entry ">The role (user or group) name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">ramemberid</entry>
                <entry colname="col2" class="- topic/entry ">The role object ID of the role that is
                  a member of this role.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">ramembername</entry>
                <entry colname="col2" class="- topic/entry ">Name of the role that is a member of
                  this role.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic38" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title id="ie192708" class="- topic/title ">Checking Database Object Sizes and Disk
      Space</title>

The <codeph class="+ topic/ph pr-d/codeph ">gp_size_*</codeph> family of views can be used to determine the disk space usage for a
        distributed Greenplum Database, schema, table, or index. The following views
        calculate the total size of an object across all primary segments (mirrors are not included
        in the size calculations).

          <xref href="#topic39" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic40" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic41" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic42" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic43" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic44" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic45" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic46" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic47" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic48" type="topic" format="dita" class="- topic/xref "/>

The table and index sizing views list the relation by object ID (not by name). To check the
        size of a table or index by name, you must look up the relation name (<codeph
          class="+ topic/ph pr-d/codeph ">relname</codeph>) in the <codeph
          class="+ topic/ph pr-d/codeph ">pg_class</codeph> table. For example:

      <codeblock>SELECT relname as name, sotdsize as size, sotdtoastsize as
toast, sotdadditionalsize as other
FROM gp_size_of_table_disk as sotd, pg_class
WHERE sotd.sotdoid=pg_class.oid ORDER BY relname;</codeblock>

    <topic id="topic39" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie192711" class="- topic/title ">gp_size_of_all_table_indexes</title>

This view shows the total size of all indexes for a table. This view is accessible to all
          users, however non-superusers will only be able to see relations that they have permission
          to access.

          <title class="- topic/title ">
            gp_size_of_all_table_indexes view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="262pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soatioid</entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soatisize</entry>
                <entry colname="col2" class="- topic/entry ">The total size of all table indexes in
                  bytes</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soatischemaname</entry>
                <entry colname="col2" class="- topic/entry ">The schema name</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soatitablename</entry>
                <entry colname="col2" class="- topic/entry ">The table name</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic40" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie179902" class="- topic/title ">gp_size_of_database </title>

This view shows the total size of a database. This view is accessible to all users,
          however non-superusers will only be able to see databases that they have permission to
          access.

          <title class="- topic/title ">gp_size_of_database
            view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="261pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sodddatname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the database</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sodddatsize</entry>
                <entry colname="col2" class="- topic/entry ">The size of the database in
                  bytes</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic41" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie179692" class="- topic/title ">gp_size_of_index</title>

This view shows the total size of an index. This view is accessible to all users, however
          non-superusers will only be able to see relations that they have permission to access.

          <title class="- topic/title ">
            gp_size_of_index view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="262pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soioid </entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the index</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soitableoid </entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the table to which the
                  index belongs</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soisize </entry>
                <entry colname="col2" class="- topic/entry ">The size of the index in bytes</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soiindexschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the index schema</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soiindexname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the index</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soitableschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the table schema</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">soitablename</entry>
                <entry colname="col2" class="- topic/entry ">The name of the table</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic42" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie179913" class="- topic/title ">gp_size_of_partition_and_indexes_disk </title>

This view shows the size on disk of partitioned child tables and their indexes. This view
          is accessible to all users, however non-superusers will only be able to see relations that
          they have permission to access..

          <title class="- topic/title ">gp_size_of_partition_and_indexes_disk view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="146pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="231pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sopaidparentoid</entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the parent
                  table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sopaidpartitionoid </entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the partition
                  table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sopaidpartitiontablesize</entry>
                <entry colname="col2" class="- topic/entry ">The partition table size in
                  bytes</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sopaidpartitionindexessize</entry>
                <entry colname="col2" class="- topic/entry ">The total size of all indexes on this
                  partition</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Sopaidparentschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the parent schema</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Sopaidparenttablename</entry>
                <entry colname="col2" class="- topic/entry ">The name of the parent table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Sopaidpartitionschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the partition
                  schema</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sopaidpartitiontablename</entry>
                <entry colname="col2" class="- topic/entry ">The name of the partition table</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic43" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie179915" class="- topic/title ">gp_size_of_schema_disk </title>

This view shows schema sizes for the public schema and the user-created schemas in the
          current database. This view is accessible to all users, however non-superusers will be
          able to see only the schemas that they have permission to access.

          <title class="- topic/title ">gp_size_of_schema_disk
            view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="145pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="230pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sosdnsp</entry>
                <entry colname="col2" class="- topic/entry ">The name of the schema</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sosdschematablesize</entry>
                <entry colname="col2" class="- topic/entry ">The total size of tables in the schema
                  in bytes</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sosdschemaidxsize</entry>
                <entry colname="col2" class="- topic/entry ">The total size of indexes in the schema
                  in bytes</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic44" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie183127" class="- topic/title ">gp_size_of_table_and_indexes_disk </title>

This view shows the size on disk of tables and their indexes. This view is accessible to
          all users, however non-superusers will only be able to see relations that they have
          permission to access.

          <title class="- topic/title ">gp_size_of_table_and_indexes_disk view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="148pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="228pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotaidoid</entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the parent
                  table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotaidtablesize</entry>
                <entry colname="col2" class="- topic/entry ">The disk size of the table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotaididxsize</entry>
                <entry colname="col2" class="- topic/entry ">The total size of all indexes on the
                  table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotaidschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The name of the schema</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotaidtablename</entry>
                <entry colname="col2" class="- topic/entry ">The name of the table</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic45" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie179651" class="- topic/title ">gp_size_of_table_and_indexes_licensing</title>

This view shows the total size of tables and their indexes for licensing purposes. The
          use of this view requires superuser permissions.

          <title class="- topic/title ">gp_size_of_table_and_indexes_licensing view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="169pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="207pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotailoid</entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotailtablesizedisk</entry>
                <entry colname="col2" class="- topic/entry ">The total disk size of the
                  table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotailtablesizeuncompressed</entry>
                <entry colname="col2" class="- topic/entry ">If the table is a compressed
                  append-optimized table, shows the uncompressed table size in bytes.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotailindexessize</entry>
                <entry colname="col2" class="- topic/entry ">The total size of all indexes in the
                  table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotailschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The schema name</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotailtablename</entry>
                <entry colname="col2" class="- topic/entry ">The table name</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic46" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie179719" class="- topic/title ">gp_size_of_table_disk </title>

This view shows the size of a table on disk. This view is accessible to all users,
          however non-superusers will only be able to see tables that they have permission to
          access

          <title class="- topic/title ">gp_size_of_table_disk
            view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="262pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotdoid</entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotdsize</entry>
                <entry colname="col2" class="- topic/entry ">The size of the table in bytes. The
                  size is only the main table size. The size does not include auxiliary objects such
                  as oversized (toast) attributes, or additional storage objects for AO
                  tables.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotdtoastsize</entry>
                <entry colname="col2" class="- topic/entry ">The size of the TOAST table (oversized
                  attribute storage), if there is one.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotdadditionalsize</entry>
                <entry colname="col2" class="- topic/entry ">Reflects the segment and block
                  directory table sizes for append-optimized (AO) tables.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotdschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The schema name</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotdtablename</entry>
                <entry colname="col2" class="- topic/entry ">The table name</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic47" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie183456" class="- topic/title ">gp_size_of_table_uncompressed</title>

This view shows the uncompressed table size for append-optimized (AO) tables. Otherwise,
          the table size on disk is shown. The use of this view requires superuser permissions.

          <title class="- topic/title ">gp_size_of_table_uncompressed
            view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="114pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="262pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotuoid</entry>
                <entry colname="col2" class="- topic/entry ">The object ID of the table</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotusize</entry>
                <entry colname="col2" class="- topic/entry ">The uncomressed size of the table in
                  bytes if it is a compressed AO table. Otherwise, the table size on disk.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotuschemaname</entry>
                <entry colname="col2" class="- topic/entry ">The schema name</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sotutablename</entry>
                <entry colname="col2" class="- topic/entry ">The table name</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic48" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie194115" class="- topic/title ">gp_disk_free</title>

This external table runs the <codeph class="+ topic/ph pr-d/codeph ">df</codeph> (disk
          free) command on the active segment hosts and reports back the results. Inactive mirrors
          are not included in the calculation. The use of this external table requires superuser
          permissions.

          <title class="- topic/title ">gp_disk_free external table</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="139pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="238pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">dfsegment </entry>
                <entry colname="col2" class="- topic/entry ">The content id of the segment (only
                  active segments are shown)</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">dfhostname</entry>
                <entry colname="col2" class="- topic/entry ">The hostname of the segment
                  host</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">dfdevice</entry>
                <entry colname="col2" class="- topic/entry ">The device name</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">dfspace </entry>
                <entry colname="col2" class="- topic/entry ">Free disk space in the segment file
                  system in kilobytes</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
  <topic id="topic49" xml:lang="en" ditaarch:DITAArchVersion="1.1"
    domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
    class="- topic/topic ">
    <title id="ie183628" class="- topic/title ">Checking for Uneven Data Distribution</title>

All tables in Greenplum Database are distributed, meaning their data is divided across all
        of the segments in the system. If the data is not distributed evenly, then query processing
        performance may suffer. The following views can help diagnose if a table has uneven data
        distribution:

          <xref href="#topic50" type="topic" format="dita" class="- topic/xref "/>

          <xref href="#topic51" type="topic" format="dita" class="- topic/xref "/>

    <topic id="topic50" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie194177" class="- topic/title ">gp_skew_coefficients</title>

This view shows data distribution skew by calculating the coefficient of variation (CV)
          for the data stored on each segment. This view is accessible to all users, however
          non-superusers will only be able to see tables that they have permission to access

          <title class="- topic/title ">gp_skew_coefficients view</title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="109pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="268pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">skcoid </entry>
                <entry colname="col2" class="- topic/entry ">The object id of the table.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">skcnamespace</entry>
                <entry colname="col2" class="- topic/entry ">The namespace where the table is
                  defined.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">skcrelname</entry>
                <entry colname="col2" class="- topic/entry ">The table name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">skccoeff </entry>
                <entry colname="col2" class="- topic/entry ">The coefficient of variation (CV) is
                  calculated as the standard deviation divided by the average. It takes into account
                  both the average and variability around the average of a data series. The lower
                  the value, the better. Higher values indicate greater data skew.</entry>
              </row>

          </tgroup>

    </topic>
    <topic id="topic51" xml:lang="en" ditaarch:DITAArchVersion="1.1"
      domains="(topic ui-d) (topic hi-d) (topic pr-d) (topic sw-d)                          (topic ut-d) (topic indexing-d)"
      class="- topic/topic ">
      <title id="ie173448" class="- topic/title ">gp_skew_idle_fractions</title>

This view shows data distribution skew by calculating the percentage of the system that
          is idle during a table scan, which is an indicator of <ph class="- topic/ph ">processing
            data skew</ph>. This view is accessible to all users, however non-superusers will only
          be able to see tables that they have permission to access

          <title class="- topic/title ">gp_skew_idle_fractions view </title>
          <tgroup cols="2" class="- topic/tgroup ">
            <colspec colnum="1" colname="col1" colwidth="109pt" class="- topic/colspec "/>
            <colspec colnum="2" colname="col2" colwidth="267pt" class="- topic/colspec "/>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">Column</entry>
                <entry colname="col2" class="- topic/entry ">Description</entry>
              </row>

              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sifoid </entry>
                <entry colname="col2" class="- topic/entry ">The object id of the table.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sifnamespace</entry>
                <entry colname="col2" class="- topic/entry ">The namespace where the table is
                  defined.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">sifrelname</entry>
                <entry colname="col2" class="- topic/entry ">The table name.</entry>
              </row>
              <row class="- topic/row ">
                <entry colname="col1" class="- topic/entry ">siffraction </entry>
                <entry colname="col2" class="- topic/entry ">The percentage of the system that is
                  idle during a table scan, which is an indicator of uneven data distribution or
                  query processing skew. For example, a value of 0.1 indicates 10% skew, a value of
                  0.5 indicates 50% skew, and so on. Tables that have more than 10% skew should have
                  their distribution policies evaluated.</entry>
              </row>

          </tgroup>

    </topic>
  </topic>
</topic>