You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Paul Guo (JIRA)" <ji...@apache.org> on 2016/08/04 11:51:20 UTC

[jira] [Assigned] (HAWQ-980) hawq does not handle guc value with space properly

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

Paul Guo reassigned HAWQ-980:
-----------------------------

    Assignee: Paul Guo  (was: Lei Chang)

> hawq does not handle guc value with space properly
> --------------------------------------------------
>
>                 Key: HAWQ-980
>                 URL: https://issues.apache.org/jira/browse/HAWQ-980
>             Project: Apache HAWQ
>          Issue Type: Bug
>            Reporter: Paul Guo
>            Assignee: Paul Guo
>
> 1. Set guc value with space in "alter database" could lead subsequent query fails.
> e.g.
>   alter database test_db set datestyle to 'postgres, MDY';
>   select * from test_table;
> One example of the error output is:
> ERROR:  Error dispatching to seg0 localhost:40000: connection pointer is NULL
> > DETAIL:
> > Master unable to connect to seg0 localhost:40000: FATAL:  invalid command-line arguments for server process
> > HINT:  Try "postgres --help" for more information.
> 2. Currently hawq dispatch code addOneOption() removes all spaces for guc value strings it handles. This is wrong since space in guc value could be meaningful.



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