PG_BLOCKLISTS
PG_BLOCKLISTS records query filtering rules. This system catalog is supported only by clusters of version 9.1.0.100 or later.
Name |
Type |
Description |
---|---|---|
block_name |
name |
Name of a query filtering rule |
role |
oid |
User OID bound to the query filtering rule |
client_addr |
inet |
IP address of the client bound to the query filtering rule |
application_name |
name |
Name of the client bound to the query filtering rule |
unique_sql_id |
int8 |
unique_sql_id that matches the query filtering rule |
sql_hash |
name |
sql_hash that matches the query filtering rule |
block_type |
int4 |
Type of the statement bound to the query filtering rule. The type can be SELECT, UPDATE, INSERT, DELETE, or MERGE. |
partition_num |
int4 |
Estimated maximum number of partitions to be scanned |
table_num |
int4 |
Estimated maximum number of tables to be scanned |
estimate_row |
int4 |
Estimated maximum number of rows to be scanned |
query_band |
text |
Type of the job that is actively identified |
sql |
text |
SQL statement that matches the query filtering rule |
created_time |
timestamp with time zone |
Timestamp when a query filtering rule is created or modified |
resource_pool |
name |
Name of the resource pool to which the statement intercepted by the query filtering rule is switched. This column is available only in clusters of version 9.1.0.200 or later. |
max_active_num |
integer |
Maximum number of concurrent statements intercepted by the query filtering rule. If the value is lower than the specified limit, execution proceeds normally. However, if the value is equal to or exceeds the limit, an error is reported and the statements are intercepted. This column is available only in clusters of version 9.1.0.200 or later. |
is_warning |
boolean |
Whether an error or alarm is reported when a statement is intercepted by the query filtering rule.
This column is available only in clusters of version 9.1.0.200 or later. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.