Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cFN0E-0007SC-Sv for pgsql-admin@arkaria.postgresql.org; Fri, 09 Dec 2016 15:22:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cFN0E-0002wp-BO for pgsql-admin@arkaria.postgresql.org; Fri, 09 Dec 2016 15:22:26 +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 1cFMyB-0001nr-C8 for pgsql-admin@postgresql.org; Fri, 09 Dec 2016 15:20:19 +0000 Received: from mail-qk0-x233.google.com ([2607:f8b0:400d:c09::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cFMy4-0001Zg-Jw for pgsql-admin@postgresql.org; Fri, 09 Dec 2016 15:20:18 +0000 Received: by mail-qk0-x233.google.com with SMTP id n204so20294319qke.2 for ; Fri, 09 Dec 2016 07:20:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version; bh=44zevYT+Yjrmemr1rufrgbObIgDZPST60waL/PoxpKc=; b=gwnQ6ahDaaGjQmDTEbiTpsGtsLr/95vPTwvwP5a4X6gPQlscgXbYmLqoOB7L2zTpo+ z/UxFl7/foX6H490M1vP7qnauIiwpuNXxM7CTlG9emdVmtyxMA8qXA5bDpkq8oVBFyOw 44slCVRQakpzmFckPIsZTEMM/DRykxwWCD5cz0baMgblmwKRemEMZvvn8gR5VHwxCcWW vxLXgf6yTzjyLazJWUMbwVoEyMp2AHknV7K1pxROI1XxPnoxReFnNm4ns7Qh1BXYbROW ZwF/ctCxN3qM5sK1Z1FK1wRo8Tp+mGnCQx3O9hYEeii8V9B8ryQM8M4w/SqlX4RY8y0W 6oFA== 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=44zevYT+Yjrmemr1rufrgbObIgDZPST60waL/PoxpKc=; b=mvmIXoslT/xc36n76OeY9HwgGxELtG2IebGvOsdv5TOG5N3iFF5Nzo8/7T4xvS581z Dkqkon+vVlhGWtt+gwTgwNX3kaFk7hsHfl22Fvm8w/Qzg1TixE8/tR4PDabhwo2NV5aT 0jXS5DD1hUiaAj1aN3TYQooQNWtpic1mBGfsfS6SfTg9t45Ks74zAsL6ZekUxyotfIFs 2EIAZhv4U+wCGKLppxOL/cPQjAhL0+N2stJ5wqdNzT16o5a1bwdaUxyOCgaE7V9TSBgV mkD49VpMkG9aiZDNTCc6CjVPu1YZoz8zQxnLYqCRaKyoHrcPs3dQ8BvMa1RxZh0VjcBz yWFA== X-Gm-Message-State: AKaTC03K0DzXIAb6ahKzcAhvu7zodcFJFtylbjnLip/MIVcTsEWt75LyLAMEbTzZPGp4YA== X-Received: by 10.55.83.7 with SMTP id h7mr78869191qkb.104.1481296811433; Fri, 09 Dec 2016 07:20:11 -0800 (PST) Received: from stell.cns.vt.edu ([2001:468:c80:2102:8b3:6047:f4dc:71e9]) by smtp.googlemail.com with ESMTPSA id w8sm19983475qta.25.2016.12.09.07.20.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Dec 2016 07:20:10 -0800 (PST) To: "pgsql-admin@postgresql.org" From: Ray Stell Subject: change PID/GID Message-ID: Date: Fri, 9 Dec 2016 10:20:09 -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="------------F6E2BA21D4F800BEF38D8169" X-Pg-Spam-Score: -2.7 (--) 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. --------------F6E2BA21D4F800BEF38D8169 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) --------------F6E2BA21D4F800BEF38D8169 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)

--------------F6E2BA21D4F800BEF38D8169--