GLOBAL_STATEMENT_COMPLEX_HISTORY
Displays workload management information about completed jobs executed on each node, as described in Table 1.
Name |
Type |
Description |
---|---|---|
datid |
oid |
OID of the database that the backend is connected to. |
dbname |
text |
Name of the database that the backend is connected to. |
schemaname |
text |
Schema name. |
nodename |
text |
Name of the CN where the statement is executed. |
username |
text |
Username used for connecting to the backend. |
application_name |
text |
Name of the application connected to the backend. |
client_addr |
inet |
IP address of the client connected to the backend. If this column is NULL, it indicates either the client is connected via a Unix socket on the server or this is an internal thread, such as AUTOVACUUM. |
client_hostname |
text |
Host name of the connected client, as reported by a reverse DNS lookup of client_addr. This column will be non-null only for IP connections and only when log_hostname is enabled. |
client_port |
integer |
TCP port number that the client uses for communication with this backend (–1 if a Unix socket is used). |
query_band |
text |
Job type, which is specified by the GUC parameter query_band. The default value is a null string. |
block_time |
bigint |
Duration that the statement is blocked before being executed, including the statement parsing and optimization duration (unit: ms). |
start_time |
timestamp with time zone |
Time when the statement execution starts. |
finish_time |
timestamp with time zone |
Time when the statement execution ends. |
duration |
bigint |
Execution time of the statement (unit: ms). |
estimate_total_time |
bigint |
Estimated execution time of the statement (unit: ms). |
status |
text |
Final statement execution status. The value can be finished (normal) or aborted (abnormal). |
abort_info |
text |
Exception information displayed if the final statement execution status is aborted. |
resource_pool |
text |
Resource pool used by the user. |
control_group |
text |
Cgroup used by the statement. |
estimate_memory |
integer |
Estimated memory used by the statement. |
min_peak_memory |
integer |
Minimum peak memory of the statement across all DNs (unit: MB). |
max_peak_memory |
integer |
Maximum peak memory of the statement across all DNs (unit: MB). |
average_peak_memory |
integer |
Average memory usage during statement execution (unit: MB). |
memory_skew_percent |
integer |
Memory usage skew of the statement among each DN. |
spill_info |
text |
Statement spill information on all DNs.
|
min_spill_size |
integer |
Minimum spilled data among all DNs when a spill occurs (unit: MB; default value: 0). |
max_spill_size |
integer |
Maximum spilled data among all DNs when a spill occurs (unit: MB; default value: 0). |
average_spill_size |
integer |
Average spilled data among all DNs when a spill occurs (unit: MB; default value: 0). |
spill_skew_percent |
integer |
DN spill skew when a spill occurs. |
min_dn_time |
bigint |
Minimum execution time of the statement across all DNs (unit: ms). |
max_dn_time |
bigint |
Maximum execution time of the statement across all DNs (unit: ms). |
average_dn_time |
bigint |
Average execution time of the statement across all DNs (unit: ms). |
dntime_skew_percent |
integer |
Execution time skew of the statement among each DN. |
min_cpu_time |
bigint |
Minimum CPU time of the statement across all DNs (unit: ms). |
max_cpu_time |
bigint |
Maximum CPU time of the statement across all DNs (unit: ms). |
total_cpu_time |
bigint |
Total CPU time of the statement across all DNs (unit: ms). |
cpu_skew_percent |
integer |
CPU time skew of the statement among DNs. |
min_peak_iops |
integer |
Minimum peak IOPS of the statement across all DNs (unit: 10 thousands per second). |
max_peak_iops |
integer |
Maximum peak IOPS of the statement across all DNs (unit: 10 thousands per second). |
average_peak_iops |
integer |
Average peak IOPS of the statement across all DNs (unit: 10 thousands per second). |
iops_skew_percent |
integer |
I/O skew across DNs. |
warning |
text |
Warning. The following warnings and warnings related to Optimizing SQL Self-Diagnosis are displayed:
|
queryid |
bigint |
Internal query ID used for statement execution. |
query |
text |
Statement executed. |
query_plan |
text |
Execution plan of the statement. |
cpu_top1_node_name |
text |
Name of the node with the highest CPU usage. |
cpu_top2_node_name |
text |
Name of the node with the second highest CPU usage. |
cpu_top3_node_name |
text |
Name of the node with the third highest CPU usage. |
cpu_top4_node_name |
text |
Name of the node with the fourth highest CPU usage. |
cpu_top5_node_name |
text |
Name of the node with the fifth highest CPU usage. |
mem_top1_node_name |
text |
Name of the node with the highest memory usage. |
mem_top2_node_name |
text |
Name of the node with the second highest memory usage. |
mem_top3_node_name |
text |
Name of the node with the third highest memory usage. |
mem_top4_node_name |
text |
Name of the node with the fourth highest memory usage. |
mem_top5_node_name |
text |
Name of the node with the fifth highest memory usage. |
cpu_top1_value |
bigint |
1st CPU usage. |
cpu_top2_value |
bigint |
2nd CPU usage. |
cpu_top3_value |
bigint |
3rd CPU usage. |
cpu_top4_value |
bigint |
4th CPU usage. |
cpu_top5_value |
bigint |
5th CPU usage. |
mem_top1_value |
bigint |
1st memory usage. |
mem_top2_value |
bigint |
2nd memory usage. |
mem_top3_value |
bigint |
3rd memory usage. |
mem_top4_value |
bigint |
4th memory usage. |
mem_top5_value |
bigint |
5th memory usage. |
top_mem_dn |
text |
Top N memory usage. |
top_cpu_dn |
text |
Top N CPU usage. |
node_group |
text |
Node group of the user to which the statement belongs. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot