Date: Fri, 9 Dec 2016 17:22:56 +0100
From: hubert depesz lubaczewski <depesz@depesz.com>
To: Ray Stell <stellr@vt.edu>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: change pid/gid
Message-ID: <20161209162256.3kcftdxa366jua5r@depesz.com>
Reply-To: depesz@depesz.com
References: <d994516f-c9d5-ec89-9802-8f4bd5e8ee2b@vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <d994516f-c9d5-ec89-9802-8f4bd5e8ee2b@vt.edu>
User-Agent: NeoMutt/20161126 (1.7.1)
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Fri, Dec 09, 2016 at 10:21:43AM -0500, Ray Stell wrote:
> 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?

no real gotchas, but change \; to + so that it will be MUCH faster.

Best regards,

depesz

-- 
The best thing about modern society is how easy it is to avoid contact with it.
                                                             http://depesz.com/


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin