Subject: Re: Updated macOS start scripts
To: Mark Dilger <hornschnorter@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
References: <31338.1510763554@sss.pgh.pa.us>
 <6D443E39-13C2-4185-9FE4-B5CB416AB06E@gmail.com>
 <21689.1510772433@sss.pgh.pa.us>
 <F8F64F48-C070-41C1-A1EE-1F25836B6FAF@gmail.com>
 <173420E2-64DB-4802-9EB2-AEFB11F46045@gmail.com>
Cc: pgsql-hackers@postgreSQL.org
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <b6a8fcda-fe25-cde8-11ac-1a5fed95fbc0@2ndquadrant.com>
Date: Tue, 28 Nov 2017 16:22:02 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <173420E2-64DB-4802-9EB2-AEFB11F46045@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 11/28/17 14:07, Mark Dilger wrote:
> Upon further review, I have noticed that `pg_ctl stop` does not work once
> the org.postgresql.postgres service has been started.  I was trying to stop,
> reinstall and re-initdb and restart postgres and this service was a pita.  I had
> to go back to your osx.patch to remind myself what I had done and only then
> could I stop the service and continue my work.

But isn't that the point?  If you use this setup, you are supposed to
use launchctl to control the service, not pg_ctl.  The same applies to,
say, a systemd setup.  If you are using a process manager, then trying
to control the process outside of that process manager isn't going to
work well.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services