[
https://issues.apache.org/jira/browse/HAWQ-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012611#comment-15012611
]
ASF GitHub Bot commented on HAWQ-170:
-------------------------------------
Github user wangzw commented on the pull request:
https://github.com/apache/incubator-hawq/pull/119#issuecomment-157923324
Good to me. +1
> Rename GUC gp_vmem_protect_limit to hawq_re_memory_overcommit_max to reflect
> latest memory enforcement implementation
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HAWQ-170
> URL: https://issues.apache.org/jira/browse/HAWQ-170
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Resource Manager
> Reporter: Ruilong Huo
> Assignee: Ruilong Huo
>
> GUC gp_vmem_protect_limit was used as vmem memory quota per HAWQ segment.
> Now, we implemented resource enforcement but leveraging gp_vmem_protect_limit
> as the GUC for maximum overcommit of memory quota per HAWQ physical segment.
> It should be renamed to hawq_re_memory_overcommit_max to reflect that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
