From: Ray Stell <stellr@vt.edu>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: change pid/gid
Date: Fri, 9 Dec 2016 10:21:43 -0500
Message-ID: <d994516f-c9d5-ec89-9802-8f4bd5e8ee2b@vt.edu> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: stellr@vt.edu
Subject: Re: change pid/gid
In-Reply-To: <d994516f-c9d5-ec89-9802-8f4bd5e8ee2b@vt.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox