Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058705
--- Diff: markdown/resourcemgmt/ConfigureResourceManagement.html.md.erb ---
@@ -100,22 +100,25 @@ In some cases, you may want to specify additional
resource quotas on the query s
The following configuration properties allow a user to control resource
quotas without altering corresponding resource queues.
--
[hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html)
- [hawq\_rm\_stmt\_nvseg](../reference/guc/parameter_definitions.html)
+-
[hawq\_rm\_stmt\_vseg\_memory](../reference/guc/parameter_definitions.html)
However, the changed resource quota for the virtual segment cannot exceed
the resource queueâs maximum capacity in HAWQ.
+***Note:*** The value of `hawq_rm_stmt_vseg_memory` depends on
`hawq_rm_stmt_nvseg`, which defines the number of virtual segments used for the
query. You must set `hawq_rm_stmt_nvseg` to a value greater than 0 before
setting the memory quota for each segment with `hawq_rm_stmt_vseg_memory`.
After running a query or completing the session, the value of
`hawq_rm_stmt_nvseg` should be reset to 0 to disable the statement level
resource quota.
+
In the following example, when executing the next query statement, the
HAWQ resource manager will attempt to allocate 10 virtual segments and each
segment has a 256MB memory quota.
+
``` sql
+postgres=# SET hawq_rm_stmt_nvseg=10;
+SET
postgres=# SET hawq_rm_stmt_vseg_memory='256mb';
SET
-postgres=# SET hawq_rm_stmt_nvseg=10;
+postgres=# SELECT <x> FROM <from_item> WHERE <condition>
--- End diff --
Should at least terminate this example with a semicolon;
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
