Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cFN1U-0007Un-89 for pgsql-admin@arkaria.postgresql.org; Fri, 09 Dec 2016 15:23:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cFN1T-00064s-RO for pgsql-admin@arkaria.postgresql.org; Fri, 09 Dec 2016 15:23:43 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cFMzm-0002Rc-Ga for pgsql-admin@postgresql.org; Fri, 09 Dec 2016 15:21:58 +0000 Received: from omr1.cc.ipv6.vt.edu ([2607:b400:92:8300:0:c6:2117:b0e] helo=omr1.cc.vt.edu) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cFMzf-0001eI-QC for pgsql-admin@postgresql.org; Fri, 09 Dec 2016 15:21:57 +0000 Received: from mr4.cc.vt.edu (smtp.ipv6.vt.edu [IPv6:2607:b400:92:9:0:9d:8fcb:4116]) by omr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id uB9FLoPG005064 for ; Fri, 9 Dec 2016 10:21:50 -0500 Received: from mail-qk0-f200.google.com (mail-qk0-f200.google.com [209.85.220.200]) by mr4.cc.vt.edu (8.14.7/8.14.7) with ESMTP id uB9FLisP023410 for ; Fri, 9 Dec 2016 10:21:49 -0500 Received: by mail-qk0-f200.google.com with SMTP id k201so17942000qke.6 for ; Fri, 09 Dec 2016 07:21:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=NDA6VmaSZRfQodwbZyKWO0YeHqeYKF08B5Eitb5c4vE=; b=f6ya2eumXoktHy3EyPYQRJ3dYaF2X3E51JYo1sppxY+0domAiP4mEP9TdIX3bV2uLA w8uejl1Vij8gVsVgDnpH+bMgQo+v8s9RD+xsced6MiNzOb9sY4J0baIUIp+8J/MNUMCL 9V3V52qdHTmJqmeySmeZgx/lsdzSqCOpgwnhvWjfDyhAyDN+X5nwOguM2xa9lEKf4ZDj n5+K1teqyJV+2bnbevF96DngBYFZejuFZSPWtJC683HNc/lFegkvHpcaT9eiMnynbuZH hgSPK39VTsIsTJ/3f/Q5rMJlLgM+ZR5oiYhUhSeHFH5ayTborOTaL9E/KMtPSx3enpJJ vCLQ== X-Gm-Message-State: AKaTC03WFU/E/y8J1J7xU378Z7M2oYui6PZgfXACK9P8O6aq9x4NeFYUYShXlEFW3V2+E9UZbgOq+MCWLniaOaCokcEP+dKZqScgTuoGJw9wTv7M5+41/2dSYSsvXFb2kmOfDSECi3gtAhlIIk1F+f+O4v8Ld2rZ0kfbc7zBKCcrsglvdvaJc9P+cA1QEzaiU3Kjj8o= X-Received: by 10.55.3.2 with SMTP id 2mr78637952qkd.65.1481296904444; Fri, 09 Dec 2016 07:21:44 -0800 (PST) X-Received: by 10.55.3.2 with SMTP id 2mr78637936qkd.65.1481296904273; Fri, 09 Dec 2016 07:21:44 -0800 (PST) Received: from stell.cns.vt.edu (stell.cns.vt.edu. [128.173.8.158]) by smtp.gmail.com with ESMTPSA id i41sm20093042qtc.18.2016.12.09.07.21.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Dec 2016 07:21:43 -0800 (PST) To: "pgsql-admin@postgresql.org" From: Ray Stell Subject: change pid/gid Message-ID: Date: Fri, 9 Dec 2016 10:21:43 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------2B69901BFFBE858F8677B097" X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mr4.cc.vt.edu X-Pg-Spam-Score: -7.2 (-------) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------2B69901BFFBE858F8677B097 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Due to some external, sysadmin issues, I'm forced to change the pid/gid of the postresql user on CentOS6. I'm wondering if this plan of action has any flaws. It seemed to work in a test environment to shutdown and change the pid/gid via: find / -uid 1500 -exec chown -h 2500:2500 {} \; (as root, of course) Startup went ok, but I've not done this in production and find myself a little nervous. I'll test in a hotstandby config here in a moment. Any gotchas hiding in there? BTW, -h will change symlinks, which I found handy. -h, --no-dereference affect each symbolic link instead of any referenced file (useful only on systems that can change the ownership of a symlink) --------------2B69901BFFBE858F8677B097 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Due to some external, sysadmin issues, I'm forced to change the pid/gid of the postresql user on CentOS6.  I'm wondering if this plan of action has any flaws.  It seemed to work in a test environment to shutdown and change the pid/gid via:


    find / -uid 1500 -exec chown -h 2500:2500 {} \;        (as root, of course)


Startup went ok, but I've not done this in production and find myself a little nervous.  I'll test in a hotstandby config here in a moment.  Any gotchas hiding in there? 

BTW, -h will change symlinks, which I found handy.

    -h, --no-dereference
              affect each symbolic link instead of any referenced file (useful only on systems that can change the ownership of a symlink)
--------------2B69901BFFBE858F8677B097--