[
https://issues.apache.org/jira/browse/HAWQ-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925309#comment-15925309
]
ASF GitHub Bot commented on HAWQ-1382:
--------------------------------------
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106057640
--- Diff:
markdown/bestpractices/managing_resources_bestpractices.html.md.erb ---
@@ -110,11 +110,14 @@ ALTER RESOURCE queue1 WITH
(VSEG_RESOURCE_QUOTA='mem:2gb');
If there are only occasional queries on Parquet tables with a large page
size, use a statement level specification instead of altering the resource
queue. For example:
```sql
-SET HAWQ_RM_STMT_NVSEG=10;
-SET HAWQ_RM_STMT_VSEG_MEMORY='2gb';
-query1;
-SET HAWQ_RM_STMT_NVSEG=0;
+postgres=# SET hawq_rm_stmt_nvseg=10;
+postgres=# SET hawq_rm_stmt_vseg_memory='2gb';
+postgres=# query1;
+postgres=# SET hawq_rm_stmt_nvseg=0;
+postgres=# SET
```
+***Note:*** To enable the statement level, you must set
`hawq_rm_stmt_nvseg` to a value greater than 0 before setting
`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, as shown in the
example above.
--- End diff --
Change "To enable the statement level" to "To set the parameters at the
statement level"
> Specify necessary setup for hawq_rm_stmt_nvseg and hawq_rm_stmt_vseg_memory
> ----------------------------------------------------------------------------
>
> Key: HAWQ-1382
> URL: https://issues.apache.org/jira/browse/HAWQ-1382
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Documentation
> Reporter: Jane Beckman
> Assignee: David Yozie
> Fix For: 2.2.0.0-incubating, 2.1.0.0-incubating
>
>
> You must set hawq_rm_stmt_nvseg before setting hawq_rm_stmt_vseg_memory
> To enable statement level, users must set hawq_rm_stmt_nvseg to a number
> larger than 0, run desired query, then set it back.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
