GS_WLM_SESSION_INFO_ALL
GS_WLM_SESSION_INFO_ALL displays load management information for completed jobs executed on all CNs. (The current feature is a lab feature. Contact Huawei technical support before using it.) Only the user with the sysadmin or monitor admin permission can query this view.
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 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. |
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 starts to be executed |
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, which 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 size of 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 DNs |
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 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:
|
queryid |
bigint |
Internal query ID used for statement execution |
query |
text |
Statement 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.) |
cpu_top1_node_name |
text |
Name of the node with the 1st CPU usage |
cpu_top2_node_name |
text |
Name of the node with the 2nd CPU usage |
cpu_top3_node_name |
text |
Name of the node with the 3rd CPU usage |
cpu_top4_node_name |
text |
Name of the node with the 4th CPU usage |
cpu_top5_node_name |
text |
Name of the node with the 5th CPU usage |
mem_top1_node_name |
text |
Name of the node with the 1st memory usage |
mem_top2_node_name |
text |
Name of the node with the 2nd memory usage |
mem_top3_node_name |
text |
Name of the node with the 3rd memory usage |
mem_top4_node_name |
text |
Name of the node with the 4th memory usage |
mem_top5_node_name |
text |
Name of the node with the 5th memory usage |
cpu_top1_value |
bigint |
CPU usage |
cpu_top2_value |
bigint |
CPU usage |
cpu_top3_value |
bigint |
CPU usage |
cpu_top4_value |
bigint |
CPU usage |
cpu_top5_value |
bigint |
CPU usage |
mem_top1_value |
bigint |
Memory usage |
mem_top2_value |
bigint |
Memory usage |
mem_top3_value |
bigint |
Memory usage |
mem_top4_value |
bigint |
Memory usage |
mem_top5_value |
bigint |
Memory usage |
top_mem_dn |
text |
Top N memory usage |
top_cpu_dn |
text |
Top N CPU usage |
n_returned_rows |
bigint |
Number of rows in the result set returned by the SELECT statement |
n_tuples_fetched |
bigint |
Number of rows randomly scanned |
n_tuples_returned |
bigint |
Number of rows sequentially scanned |
n_tuples_inserted |
bigint |
Number of rows inserted |
n_tuples_updated |
bigint |
Number of rows updated |
n_tuples_deleted |
bigint |
Number of rows deleted |
n_blocks_fetched |
bigint |
Number of buffer block access times |
n_blocks_hit |
bigint |
Number of buffer block hits |
db_time |
bigint |
Valid DB time, which is accumulated if multiple threads are involved (unit: μs) |
cpu_time |
bigint |
CPU time (unit: μs) |
execution_time |
bigint |
Execution time in the executor (unit: μs) |
parse_time |
bigint |
SQL parsing time (unit: μs) |
plan_time |
bigint |
SQL plan generation time (unit: μs) |
rewrite_time |
bigint |
SQL rewriting time (unit: μs) |
pl_execution_time |
bigint |
Execution time of PL/pgSQL (unit: μs) |
pl_compilation_time |
bigint |
Compilation time of PL/pgSQL (unit: μs) |
net_send_time |
bigint |
Network time (unit: μs) |
data_io_time |
bigint |
I/O time (unit: μs) |
is_slow_query |
bigint |
Whether the record is a slow SQL record. |
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