[jira] [Resolved] (HAWQ-33) Change initdb log location to avoid giving write privileges to gpadmin user on parent hawq data dir.

["Radar Lei (JIRA)" <ji...@apache.org>]

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

Radar Lei resolved HAWQ-33.
---------------------------
    Resolution: Fixed

> Change initdb log location to avoid giving write privileges to gpadmin user on parent hawq data dir. 
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HAWQ-33
>                 URL: https://issues.apache.org/jira/browse/HAWQ-33
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Command Line Tools
>            Reporter: Radar Lei
>            Assignee: Radar Lei
>            Priority: Minor
>
> During init of a postgres instance, initdb logs are generated and placed under parent of the hawq directory input provied. Ex: If we mentioned /data/hawq-master,  log generated will be /data/hawq-master.initdb. It suggests that /data should have write permission for gpadmin.
> Consider, if the user has provided the directory as /hawq-master, which will require '/' root directory to have permission for gpadmin to write the logs, which will be unacceptable at many customer's site.
> We should change the location of the initdb logs created and they should be under /tmp or /home/gpadmin/hawqAdminLogs or some other directory.
> ```
> selecting default max_connections ... sh: /data/hawq-master.initdb: Permission denied
> initdb: error 256 from: "/usr/local/hawq-2.0.0.0/bin/postgres" --boot -x0 -F -c max_connections=1280 -c shared_buffers=4000 -c max_fsm_pages=200000 < "/dev/null" > "/data/hawq-master.initdb" 2>&1
> [root@ip-10-32-37-245 ~]# less /data/hawq-master.initdb
> PostgreSQL stand-alone backend 8.2.15
> backend> backend> backend> backend>
> ```



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