You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hawq.apache.org by "Ruilong Huo (JIRA)" <ji...@apache.org> on 2016/04/14 16:05:26 UTC

[jira] [Resolved] (HAWQ-666) Restore to correct memory context after free query resource in ExecutorEnd

     [ https://issues.apache.org/jira/browse/HAWQ-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruilong Huo resolved HAWQ-666.
------------------------------
    Resolution: Fixed

> Restore to correct memory context after free query resource in ExecutorEnd
> --------------------------------------------------------------------------
>
>                 Key: HAWQ-666
>                 URL: https://issues.apache.org/jira/browse/HAWQ-666
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-beta-incubating
>            Reporter: Ruilong Huo
>            Assignee: Ruilong Huo
>             Fix For: 2.0.0
>
>
> In ExecutorEnd, we need to restore to correct memory context after free query resource. There are two memory context based on PG_TRY of mppExecutorFinishup:
> 1. If mppExecutorFinishup completes successfully, the correct memory context is estate->es_query_cxt
> 2. If mppExecutorFinishup errors, the correct memory context is ErrorContext
> Current implementation use estate->es_query_cxt for both situation. We need to fix this as it may lead to core dump during memory context cleanup afterwards.



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