hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jiny2 <...@git.apache.org>
Subject [GitHub] incubator-hawq pull request: HAWQ-47. Make user able to set statem...
Date Thu, 22 Oct 2015 00:04:45 GMT
GitHub user jiny2 opened a pull request:


    HAWQ-47. Make user able to set statement level resource usage.

    user can use the following statements to set statement level resource quota. When statement
level resource quota is active, target hawq resource queue setting is almost all ignored,
only the resource queue capacity is considered, i.e. user can not set resource quota more
than maximum capacity of the target queue. 
    the vseg memory can only be chosen from finite value sets : 128mb, 256mb, 512mb, 1024mb/1gb,
2048mb/2gb, 4096mb/4gb, ..., 16384mb/16gb
    postgres=# show hawq_rm_stmt_nvseg;
    (1 row)
    postgres=# show hawq_rm_stmt_vseg_memory;
    (1 row)
    postgres=# set hawq_rm_stmt_nvseg=8;
    postgres=# set hawq_rm_stmt_vseg_memory='1gb';
    postgres=# insert into t values(1);
    INSERT 0 1
    postgres=# set hawq_rm_stmt_nvseg=10;   -- in case setting too much resource!
    postgres=# insert into t values(1);
    ERROR:  failed to acquire resource because of remote error expecting too many virtual
segments. (pquery.c:798)
    Some error message refinement changes are also included.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jiny2/incubator-hawq HAWQ-47

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #34
commit 2c6afa51923701f81aa7ed0f1736bfc44e1f44a3
Author: Yi Jin <yjin@pivotal.io>
Date:   2015-10-21T23:56:24Z

    HAWQ-47. Make user able to set statement level resource usage.


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.

View raw message