You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Ming LI (JIRA)" <ji...@apache.org> on 2016/02/16 10:37:18 UTC

[jira] [Commented] (HAWQ-214) Build-in functions for gp_partition will cause cores.

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

Ming LI commented on HAWQ-214:
------------------------------

It seems that all these partition management functions are introduced for the ORCA optimizer. The variable dynamicTableScanInfo will point to the value initialized in EState during dynamic table scan execution. 

These functions are not designed for user to call directly, the use case above is not correct. So I will close it as designed.


> Build-in functions for gp_partition will cause cores.
> -----------------------------------------------------
>
>                 Key: HAWQ-214
>                 URL: https://issues.apache.org/jira/browse/HAWQ-214
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Unknown
>            Reporter: Dong Li
>            Assignee: Ming LI
>             Fix For: 2.0.0
>
>
> There are four build-in functions for gp_patition , and all of them will cause core.
> gp_partition_expansion
> gp_partition_inverse
> gp_partition_propagation
> gp_partition_selection
> {code}
> create table pt_table(a int, b int) distributed by (a) partition by range(b) (default partition others,start(1) end(100) every(10));
> {code}
> {code}
> e=# select pg_catalog.gp_partition_selection(16550,1);
> FATAL:  Unexpected internal error (gp_partition_functions.c:197)
> DETAIL:  FailedAssertion("!(dynamicTableScanInfo != ((void *)0))", File: "gp_partition_functions.c", Line: 197)
> HINT:  Process 22247 will wait for gp_debug_linger=120 seconds before termination.
> Note that its locks and other resources will not be released until then.
> server closed the connection unexpectedly
> 	This probably means the server terminated abnormally
> 	before or while processing the request.
> The connection to the server was lost. Attempting reset: Succeeded.
> {code}



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