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

Ming LI commented on HAWQ-1068:
-------------------------------

Add check for this function:

postgres=# select get_ao_compression_ratio(null);
ERROR:  failed to get relname for this function. (aosegfiles.c:1553)
postgres=# select get_ao_compression_ratio(0);
ERROR:  failed to get valid relation id for this function. (aosegfiles.c:1575)

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

Reply via email to