GS_BLOCKLIST_QUERY
GS_BLOCKLIST_QUERY records job blocklist and exception information. This table uses unique_sql_id as the unique index to collect statistics on job exception information and record blocklist information. You can associate GS_BLOCKLIST_QUERY with GS_WLM_SESSION_INFO to obtain the query column and execution information of a job.
GaussDB(DWS) also provides the GS_BLOCKLIST_QUERY view for querying job blocklist and exception information. This view can directly display the query column. This view depends on GS_WLM_SESSION_INFO. If the GS_WLM_SESSION_INFO table is large, the query may take a long time.
Name |
Type |
Reference |
Description |
---|---|---|---|
unique_sql_id |
bigint |
N/A |
Query ID generated based on the query parsing tree. |
block_list |
boolean |
N/A |
Check whether a job is in the blocklist. |
except_num |
integer |
N/A |
Query the number of job exceptions. |
except_time |
timestamp |
N/A |
Query the time when the last job exception occurred. |
- The schema of this system catalog is dbms_om.
- This system catalog contains unique indexes, which are distributed on DNs in hash mode. The distributed column is unique_sql_id.
- This system catalog can be queried only in the gaussdb database. If it is queried in other databases, an error will be reported.
- The GS_BLOCKLIST_QUERY view is stored in pg_catalog.
- Generally, constant values are ignored during unique SQL ID calculation in DML statements. However, constant values cannot be ignored in DDL, DCL, and parameter setting statements. A unique_sql_id may correspond to one or more queries.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.