| From: | Ray Stell <stellr(at)vt(dot)edu> |
|---|---|
| To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | change pid/gid |
| Date: | 2016-12-09 15:21:43 |
| Message-ID: | d994516f-c9d5-ec89-9802-8f4bd5e8ee2b@vt.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-09 15:33:58 | Re: change pid/gid |
| Previous Message | Ray Stell | 2016-12-09 15:20:09 | change PID/GID |