Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
Date: Thu, 22 Sep 2016 07:13:20 +0000 (UTC)
From: "Ming LI (JIRA)" <jira@apache.org>
To: dev@hawq.incubator.apache.org
Message-ID: <JIRA.13006768.1474528390000.635318.1474528400536@Atlassian.JIRA>
In-Reply-To: <JIRA.13006768.1474528390000@Atlassian.JIRA>
References: <JIRA.13006768.1474528390000@Atlassian.JIRA> <JIRA.13006768.1474528390850@arcas>
Subject: [jira] [Created] (HAWQ-1068) master process panic with signal 11
 when call get_ao_compression_ratio(null)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 22 Sep 2016 07:13:24 -0000

Ming LI created HAWQ-1068:
-----------------------------

             Summary: master process panic with signal 11 when call get_ao_compression_ratio(null)
                 Key: HAWQ-1068
                 URL: https://issues.apache.org/jira/browse/HAWQ-1068
             Project: Apache HAWQ
          Issue Type: Bug
          Components: Catalog
            Reporter: Ming LI
            Assignee: Lei Chang
             Fix For: backlog


Customer has a function which will call get_ao_compression_ratio() to pass the relation name dynamically. However in some corner case get_ao_compression_ratio() will be passed with NULL, which triggered a signal 11 and crashed the master process. 
The issue could be easily reproduced in house as shown below:
gpadmin=# select get_ao_compression_ratio(null);
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: Failed.
!> \q


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