GS_WLM_SESSION_HISTORY
GS_WLM_SESSION_HISTORY displays load management information about a completed job executed by the current user on the current CN. (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.
The data in GaussDB is deleted every 3 minutes. If the GUC parameter enable_resource_record is set to on, the records in the view are dumped to the GS_WLM_SESSION_QUERY_INFO_ALL system catalog every 3 minutes and deleted from the view. If enable_resource_record is set to off, the records are retained in the view for 3 minutes and then deleted.
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 that is connected to the backend |
client_addr |
inet |
IP address of the client connected to the backend. If this column is null, either the client is connected via a Unix socket on the server machine 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 only be non-null 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 (in ms) that a statement is blocked before being executed, including the statement parsing and optimization duration |
start_time |
timestamp with time zone |
Time when the statement starts to run |
finish_time |
timestamp with time zone |
Time when the statement execution ends |
duration |
bigint |
Execution time of the statement, in ms |
estimate_total_time |
bigint |
Estimated execution time of the statement, in 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 memory peak of the statement across all DNs, in MB |
max_peak_memory |
integer |
Maximum memory peak of the statement across all DNs, in MB |
average_peak_memory |
integer |
Average memory usage during statement execution, in 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, in MB (default value: 0) |
max_spill_size |
integer |
Maximum spilled data among all DNs when a spill occurs, in MB (default value: 0) |
average_spill_size |
integer |
Average spilled data among all DNs when a spill occurs, in 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, in ms |
max_dn_time |
bigint |
Maximum execution time of the statement across all DNs, in ms |
average_dn_time |
bigint |
Average execution time of the statement across all DNs, in 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, in ms |
max_cpu_time |
bigint |
Maximum CPU time of the statement across all DNs, in ms |
total_cpu_time |
bigint |
Total CPU time of the statement across all DNs, in ms |
cpu_skew_percent |
integer |
CPU time skew of the statement among DNs |
min_peak_iops |
integer |
Minimum IOPS peak 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 IOPS peak 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 IOPS peak 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 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 |
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 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 CPU usage |
mem_top3_node_name |
text |
Name of the node with the third highest CPU usage |
mem_top4_node_name |
text |
Name of the node with the fourth highest CPU usage |
mem_top5_node_name |
text |
Name of the node with the fifth highest CPU 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 |
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