WORKLOAD_ROUTING_RULES
Lists the routing rules that map workloads to a subcluster.
	Lists the routing rules that map workloads to subclusters.
| Column Name | Data Type | Description | 
|---|---|---|
| OID | INTEGER | The object identifier for the routing rule. | 
| WORKLOAD | VARCHAR | The name of the workload. When specified by a client (either as a connection property or as a session parameter with SET SESSION WORKLOAD), the client's queries are executed by the subcluster specified by the workload routing rule. | 
| SUBCLUSTER_OID | INTEGER | The object identifier for the Subcluster. | 
| SUBCLUSTER_NAME | VARCHAR | The subcluster that contains the Execution node that executes client queries for its associated workload. | 
| PRIORITY | INTEGER | A non-negative INTEGER, the priority of the workload. The greater the value, the greater the priority. If a user or their role is granted multiple routing rules, the one with the greatest priority applies. | 
Privileges
Superuser
Examples
The following query shows two rules that define the following behavior:
- Clients with workload reportingare routed to subclusterdefault_subcluster.
- Clients with workload analyticsare randomly routed tosc_01orsc_02.
=> SELECT * FROM v_catalog.workload_routing_rules;
        oid        | workload  |  subcluster_oid   |  subcluster_name   | priority 
-------------------+-----------+-------------------+--------------------+----------
 45035996273850122 | reporting | 45035996273704962 | default_subcluster | 5
 45035996273849658 | analytics | 45035996273849568 | sc_01              | 4
 45035996273849658 | analytics | 45035996273849568 | sc_02              | 0