hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dyozie <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #103: HAWQ-1382
Date Wed, 15 Mar 2017 00:08:55 GMT
Github user dyozie commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/103#discussion_r106058647
  
    --- 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
    --- End diff --
    
    I'm pretty sure this SET command isn't actually a command to type at the postgres=# prompt,
but an output from psqsl.  See the example at the end of this PR (each SET <something>
command results in psql showing SET).  You should make both code blocks similar in this regard.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message