hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yaoj2 <...@git.apache.org>
Subject [GitHub] incubator-hawq pull request: HAWQ-367. Introduce seg_max_connectio...
Date Thu, 28 Jan 2016 03:46:10 GMT
Github user yaoj2 commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq/pull/301#discussion_r51076744
  
    --- Diff: src/backend/utils/misc/guc.c ---
    @@ -4617,6 +4617,20 @@ static struct config_int ConfigureNamesInt[] =
     		200, 10, MAX_MAX_BACKENDS, NULL, NULL
     	},
     
    +	/*
    +	 * When HAWQ has one master and one segment deployed together in one physical
    +	 * machine, we can not separately set different max connection count. Thus,
    +	 * we introduce this guc for segment setting only.
    +	 */
    +	{
    +		{"seg_max_connections", PGC_POSTMASTER, CONN_AUTH_SETTINGS,
    +			gettext_noop("Sets the maximum number of concurrent connections in a segment."),
    +			NULL
    +		},
    +		&SegMaxBackends,
    +		1600, 80, MAX_MAX_BACKENDS, NULL, NULL
    +	},
    +
    --- End diff --
    
    For default value, according to 1.x  the default is 3 times master value. So we use 200
as master value then 200*3 * 8 we use 4800 as default value.


---
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