User guide

of range for the cluster. If you change the parameter value and want to return to the default setting, reset
the parameter to 0.
After you change this value, and restart the cluster, you can query STV_CURSOR_CONFIGURATION
to make sure that the values took effect.
When running queries, if you get the following error, consider decreasing the
max_cursor_result_set_size value:
"Exceeded the maximum number of cursors allowed to be open concurrently. Analyze the current state
with stv_active_cursors and the current configuration via stv_cursor_configuration, and consider decreasing
the value of the max_cursor_result_set_size configuration parameter to increase the degree of parallelism."
Conversely, if you get the following error when running queries, consider increasing the
max_cursor_result_set_size value:
"Exceeded the maximum size allowed for the result set of a cursor operation. Current size: size. Analyze
the current configuration via stv_cursor_configuration, and consider increasing the value of the
max_cursor_result_set_size configuration parameter."
Configuring Workload Management
In Amazon Redshift, you use workload management (WLM) to define the number of query queues that
are available, and how queries are routed to those queues for processing. WLM is part of parameter
group configuration. A cluster uses the WLM configuration that is specified in its associated parameter
group.
You can configure WLM by using the Amazon Redshift console, the AWS CLI, Amazon Redshift API, or
one of the AWS SDKs.WLM configuration comprises several properties to define queue behavior, such
as memory allocation across queues, the number of queries that can run concurrently in a queue, and
so on. The following list describes the WLM properties that you can configure for each queue.
API Version 2012-12-01
59
Amazon Redshift Management Guide
Configuring Workload Management