Skip to content
Permalink
Browse files
HAWQ-1217 Format cleanup (This closes #72)
  • Loading branch information
dyozie committed Dec 14, 2016
1 parent f152b5c commit 5e7285e5041d2b56012719e35464d5e59d258643
Show file tree
Hide file tree
Showing 16 changed files with 27 additions and 27 deletions.
@@ -11,7 +11,7 @@ The `gp_master_mirroring` table contains state information about the standby mas
|-----------------|--------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `summary_state` | text |   | The current state of the log replication process between the master and standby master - logs are either ‘Synchronized’ or ‘Not Synchronized’ |
| `detail_state` | text |   | If not synchronized, this column will have information about the cause of the error. |
| `log_time` | timestamp with time zone |   | This contains the timestamp of the last time a master mirroring change occurred. For example, the timestamp when the value of summary\_state changed from "Synchronized" to "Not Synchronized". If no changes occur with regards to the standby master (it stays synchronized), the timestamp is not updated. |
| `log_time` | timestamp with time zone |   | This contains the timestamp of the last time a master mirroring change occurred. For example, the timestamp when the value of `summary_state` changed from "Synchronized" to "Not Synchronized". If no changes occur with regards to the standby master (it stays synchronized), the timestamp is not updated. |
| `error_message` | text |   | If not synchronized, this column will have the error message from the failed synchronization attempt. |


@@ -4,19 +4,19 @@ title: gp_segment_configuration

The `gp_segment_configuration` table contains information about master, standby and segment configuration.

The HAWQ fault tolerance service (FTS) automatically detects the status of individual segments and marks the status of each segment in this table. If a segment is marked as DOWN, the corresponding reason is recorded in the [gp_configuration_history](gp_configuration_history.html) table. See [Understanding the Fault Tolerance Service](../../admin/FaultTolerance.html) for a description of the fault tolerance service.
The HAWQ fault tolerance service (FTS) automatically detects the status of individual segments and marks the status of each segment in this table. If a segment is marked as DOWN, the corresponding reason is recorded in the [gp\_configuration\_history](gp_configuration_history.html) table. See [Understanding the Fault Tolerance Service](../../admin/FaultTolerance.html) for a description of the fault tolerance service.

<a id="topic1__fr163962"></a>
<span class="tablecap">Table 1. pg\_catalog.gp\_segment\_configuration</span>

| column | type | references | description |
|----------------------|---------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `registration_order` | integer |   | When HAWQ starts, the master and each segment starts itself separately. This column indicates the order in which a segment node registers itself to master node. The registration\_order for segments starts from 1. Master's registration\_order is 0. Standby's registration\_order is -1. |
| `registration_order` | integer |   | When HAWQ starts, the master and each segment starts itself separately. This column indicates the order in which a segment node registers itself to master node. The `registration_order` for segments starts from 1. Master's registration\_order is 0. Standby's registration\_order is -1. |
| `role` | char |   | The role that a node is currently running as. Values are `p` (segment), `m`(master) or `s `(standby). |
| `status` | char |   | The fault status of a segment. Values are `u` (up) or `d` (down). |
| `port` | integer |   | The TCP port the database server listener process is using. |
| `hostname` | text |   | The hostname of a segment host. |
| `address` | text |   | The hostname used to access a particular segment on a segment host. This value may be the same as `hostname` in systems upgraded from 3.x or on systems that do not have per-interface hostnames configured. |
| `address` | text |   | The hostname used to access a particular segment on a segment host. |
| `failed_tmpdir_num` | integer |   | The number of failed temporary directories on the segment. User- configured temporary directories may fail on segments due to disk errors. This information is reported to the master. |
| `failed_tmpdir` | text |   | A list of failed temporary directories on the segment. Multiple failed temporary directories are separated by commas. |

@@ -11,8 +11,8 @@ The `pg_appendonly` table contains information about the storage options and oth
|-----------------|----------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
| `relid` | oid |   | The table object identifier (OID) of the compressed table. |
| `compresslevel` | smallint |   | The compression level, with increasing compression ratio. If the `gzip` or `zlib` compression type is specified, valid values are 1-9. |
| `majorversion` | smallint |   | The major version number of the pg\_appendonly table. |
| `minorversion` | smallint |   | The minor version number of the pg\_appendonly table. |
| `majorversion` | smallint |   | The major version number of the `pg_appendonly` table. |
| `minorversion` | smallint |   | The minor version number of the `pg_appendonly` table. |
| `checksum` | boolean |   | A checksum value that is stored to compare the state of a block of data at compression time and at scan time to ensure data integrity. |
| `compresstype` | text |   | Type of compression used on append-only and parquet tables. `zlib`, `snappy`, and `gzip` compression types are supported. |
| `columnstore` | boolean |   | `0` for row-oriented storage. |
@@ -19,10 +19,10 @@ The `pg_attribute` table stores information about table columns. There will be e
| `attcacheoff` | integer |   | Always `-1` in storage, but when loaded into a row descriptor in memory this may be updated to cache the offset of the attribute within the row |
| `atttypmod` | integer |   | Records type-specific data supplied at table creation time (for example, the maximum length of a varchar column). It is passed to type-specific input functions and length coercion functions. The value will generally be `-1` for types that do not need it. |
| `attbyval` | boolean |   | A copy of pg\_type.typbyval of this column's type |
| `attstorage` | char |   | Normally a copy of pg\_type.typstorage of this column's type. For TOAST-able data types, this can be altered after column creation to control storage policy. |
| `attalign` | char |   | A copy of pg\_type.typalign of this column's type |
| `attstorage` | char |   | Normally a copy of `pg_type.typstorage` of this column's type. For TOAST-able data types, this can be altered after column creation to control storage policy. |
| `attalign` | char |   | A copy of `pg_type.typalign` of this column's type |
| `attnotnull` | boolean |   | This represents a not-null constraint. It is possible to change this column to enable or disable the constraint. |
| `atthasdef` | boolean |   | This column has a default value, in which case there will be a corresponding entry in the pg\_attrdef catalog that actually defines the value |
| `atthasdef` | boolean |   | This column has a default value, in which case there will be a corresponding entry in the `pg_attrdef` catalog that actually defines the value |
| `attisdropped` | boolean |   | This column has been dropped and is no longer valid. A dropped column is still physically present in the table, but is ignored by the parser and so cannot be accessed via SQL |
| `attislocal` | boolean |   | This column is defined locally in the relation. Note that a column may be locally defined and inherited simultaneously |
| `attinhcount` | integer |   | The number of direct ancestors this column has. A column with a nonzero number of ancestors cannot be dropped nor renamed |
@@ -24,7 +24,7 @@ Because user identities are system-wide, `pg_authid` is shared across all databa
| `rolpassword` | text |   | Password (possibly encrypted); NULL if none |
| `rolvaliduntil` | timestamptz |   | Password expiry time (only used for password authentication); NULL if no expiration |
| `rolconfig` | text\[\] |   | Session defaults for server configuration parameters |
| `relresqueue` | oid |   | Object ID of the associated resource queue ID in *pg\_resqueue* |
| `relresqueue` | oid |   | Object ID of the associated resource queue ID in `pg_resqueue` |
| `rolcreaterextgpfd` | boolean |   | Privilege to create read external tables with the `gpfdist` or `gpfdists` protocol |
| `rolcreaterexhttp` | boolean |   | Privilege to create read external tables with the `http` protocol |
| `rolcreatewextgpfd` | boolean |   | Privilege to create write external tables with the `gpfdist` or `gpfdists` protocol |
@@ -39,7 +39,7 @@ The system catalog table `pg_class` catalogs tables and most everything else tha
<td><code class="ph codeph">reltype</code></td>
<td>oid</td>
<td>pg_type.oid</td>
<td>The OID of the data type that corresponds to this table's row type, if any (zero for indexes, which have no pg_type entry)</td>
<td>The OID of the data type that corresponds to this table's row type, if any (zero for indexes, which have no <code class="ph codeph">pg_type</code> entry)</td>
</tr>
<tr class="even">
<td><code class="ph codeph">relowner</code></td>

0 comments on commit 5e7285e

Please sign in to comment.