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 table. See Understanding the Fault Tolerance Service for a description of the fault tolerance service.
Table 1. pg_catalog.gp_segment_configuration
| 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. |
|
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. | |
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. |