diff --git a/gpdb-doc/dita/admin_guide/workload_mgmt_resgroups.xml b/gpdb-doc/dita/admin_guide/workload_mgmt_resgroups.xml index ea13190a07e0552e028eca21fc6683aaedaa16ec..5e8c9ee29518651a1542a858baf2ac9e39cc6c03 100644 --- a/gpdb-doc/dita/admin_guide/workload_mgmt_resgroups.xml +++ b/gpdb-doc/dita/admin_guide/workload_mgmt_resgroups.xml @@ -7,6 +7,42 @@

You can use resource groups to manage the number of active queries that may execute concurrently in your Greenplum Database cluster. With resource groups, you can also manage the amount of CPU and memory resources Greenplum allocates to each query.

+

This topic includes the following subtopics:

+ + + + Introduction +

When the user executes a query, Greenplum Database evaluates the query against a set of limits defined for the resource group. Greenplum Database executes the query immediately if the group's resource limits have not yet been reached and the query does not cause the group @@ -62,7 +98,8 @@ Resource limits are not enforced on SET, RESET, and SHOW commands. - + + Transaction Concurrency Limit @@ -583,5 +620,4 @@ gpstart -