[jira] [Commented] (HAWQ-367) introduce seg_max_connections guc to set segment max_connections setting

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HAWQ-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120688#comment-15120688 ] 

ASF GitHub Bot commented on HAWQ-367:
-------------------------------------

GitHub user jiny2 opened a pull request:

    https://github.com/apache/incubator-hawq/pull/301

    HAWQ-367. Introduce seg_max_connections guc to set segment max_connections setting

    

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

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

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

    https://github.com/apache/incubator-hawq/pull/301.patch

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

    This closes #301
    
----
commit 73affae221c83e7fab14bf1f174062d9d804bef1
Author: YI JIN <yj...@pivotal.io>
Date:   2016-01-28T03:25:09Z

    HAWQ-367. Introduce seg_max_connections guc to set segment max_connections setting

----


> introduce seg_max_connections guc to set segment max_connections setting
> ------------------------------------------------------------------------
>
>                 Key: HAWQ-367
>                 URL: https://issues.apache.org/jira/browse/HAWQ-367
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Interconnect
>            Reporter: Yi Jin
>            Assignee: Yi Jin
>
> In case one HAWQ master and one HAWQ segment are deployed in one physical machine, it is not possible to set different max connections in the two instances. Therefore, this new guc is introduced.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)