GLOBAL_STATEMENT_COMPLEX_RUNTIME

GLOBAL_STATEMENT_COMPLEX_RUNTIME displays load management records of jobs that are being executed by the current user on each node. (The current feature is a lab feature. Contact Huawei technical support before using it.)

**Table 1** GLOBAL_STATEMENT_COMPLEX_RUNTIME columns
Name	Type	Description
datid	oid	OID of the database that this backend is connected to
dbname	name	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	name	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 process, 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.
pid	bigint	Backend thread ID
block_time	bigint	Block time before the statement is executed (unit: ms)
start_time	timestamp with time zone	Time when the statement starts to be executed
duration	bigint	For how long the statement has been executing (unit: ms)
estimate_total_time	bigint	Estimated execution time of the statement (unit: ms)
estimate_left_time	bigint	Estimated remaining time of statement execution (unit: ms)
enqueue	text	Resource status in workload management. (The current feature is a lab feature. Contact Huawei technical support before using it.)
resource_pool	name	Resource pool used by the user
control_group	text	Cgroup used by the statement
estimate_memory	integer	Estimated memory used by the statement (unit: MB). This parameter takes effect only when enable_dynamic_workload is set to on.
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 DNs
spill_info	text	Statement spill information on all DNs. None: No data is spilled to disks on all DNs. All: Data is spilled to disks on all DNs. [a:b]: The statement has been spilled to disks on a of b 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 DNs
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. It is counted by ones in a column-store table and by ten thousands in a row-store table.
max_peak_iops	integer	Maximum peak IOPS of the statement across all DNs. It is counted by ones in a column-store table and by ten thousands in a row-store table.
average_peak_iops	integer	Average peak IOPS of the statement across all DNs. It is counted by ones in a column-store table and by ten thousands in a row-store table.
iops_skew_percent	integer	I/O skew of the statement among DNs
warning	text	Warning. The following warnings and warnings related to Optimizing SQL Self-Diagnosis are displayed: Spill file size large than 256MB Broadcast size large than 100MB Early spill Spill times is greater than 3 Spill on memory adaptive Hash table conflict
queryid	bigint	Internal query ID used for statement execution
query	text	Statement being executed
query_plan	text	Execution plan of the statement
node_group	text	Logical cluster of the user running the statement. (The current feature is a lab feature. Contact Huawei technical support before using it.)
top_cpu_dn	text	Top N CPU usage
top_mem_dn	text	Top N memory usage