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 view is used by Database Manager to query data from GaussDB(DWS). The view returns the data queried from the GS_WLM_SESSION_INFO table within three minutes only when the GUC parameter enable_resource_track is set to on.
Name |
Type |
Description |
---|---|---|
datid |
oid |
OID of the database this backend is connected to |
dbname |
text |
Name of the database the backend is connected to |
schemaname |
text |
Schema name |
nodename |
text |
Name of the CN where the statement is run |
username |
text |
User name 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 this backend. If this column is null, it indicates either that the client is connected via a Unix socket on the server machine or that 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, or -1 if a Unix socket is used |
query_band |
text |
Job type, which is specified by the query_band parameter. The default value is a null string. |
block_time |
bigint |
Duration that a statement is blocked before being executed, including the statement parsing and optimization duration. The unit is ms. |
start_time |
timestamp with time zone |
Time when the statement starts to be run |
finish_time |
timestamp with time zone |
Time when the statement execution ends |
duration |
bigint |
Execution time of a statement. The unit is ms. |
estimate_total_time |
bigint |
Estimated execution time of a statement. The unit is ms. |
status |
text |
Final statement execution status. Its value can be finished (normal) or aborted (abnormal). The statement status here is the execution status of the database server. If the statement is successfully executed on the database server but an error is reported in the result set, the statement status is finished. |
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. The unit is MB. |
min_peak_memory |
integer |
Minimum memory peak of a statement across all DNs. The unit is MB. |
max_peak_memory |
integer |
Maximum memory peak of a statement across all DNs. The unit is MB. |
average_peak_memory |
integer |
Average memory usage during statement execution. The unit is MB. |
memory_skew_percent |
integer |
Memory usage skew of a statement among DNs. |
spill_info |
text |
Statement spill information on all DNs. None indicates that the statement has not been flushed to disks on any DNs. All indicates that the statement has been spilled to disks on every DN. [a:b] indicates that 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. The default value is 0. The unit is MB. |
max_spill_size |
integer |
Minimum spilled data among all DNs when a spill occurs. The default value is 0. The unit is MB. |
average_spill_size |
integer |
Average spilled data among all DNs when a spill occurs. The default value is 0. The unit is MB. |
spill_skew_percent |
integer |
DN spill skew when a spill occurs |
min_dn_time |
bigint |
Minimum execution time of a statement across all DNs. The unit is ms. |
max_dn_time |
bigint |
Maximum execution time of a statement across all DNs. The unit is ms. |
average_dn_time |
bigint |
Average execution time of a statement across all DNs. The unit is ms. |
dntime_skew_percent |
integer |
Execution time skew of a statement among DNs. |
min_cpu_time |
bigint |
Minimum CPU time of a statement across all DNs. The unit is ms. |
max_cpu_time |
bigint |
Maximum CPU time of a statement across all DNs. The unit is ms. |
total_cpu_time |
bigint |
Total CPU time of a statement across all DNs. The unit is ms. |
cpu_skew_percent |
integer |
CPU time skew of a statement among DNs. |
min_peak_iops |
integer |
Minimum I/O peak of a statement on all DNs (times/s in column-store tables and 10,000 times/s in row-store tables). This function is not enabled in cluster version 8.1.3. Therefore, you are not advised to refer to this field to analyze memory problems. |
max_peak_iops |
integer |
Maximum I/O peak of a statement on all DNs (times/s in column-store tables and 10,000 times/s in row-store tables). This function is not enabled in cluster version 8.1.3. Therefore, you are not advised to refer to this field to analyze memory problems. |
average_peak_iops |
integer |
Average I/O peak of a statement on all DNs (times/s in column-store tables and 10,000 times/s in row-store tables). This function is not enabled in cluster version 8.1.3. Therefore, you are not advised to refer to this field to analyze memory problems. |
iops_skew_percent |
integer |
I/O skew of a statement among DNs. This function is not enabled in the 8.1.3 cluster. You are not advised to refer to this field to analyze memory problems. |
warning |
text |
Warning. The following warnings and warnings related to SQL self-diagnosis tuning are displayed:
|
queryid |
bigint |
Internal query ID used for statement execution |
query |
text |
Statement executed |
query_plan |
text |
Execution plan of a statement |
node_group |
text |
Logical cluster of the user running the statement |
pid |
bigint |
PID of the backend thread of the statement |
lane |
text |
Fast/Slow lane where the statement is executed |
unique_sql_id |
bigint |
ID of the normalized unique SQL. |
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