From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Dilger <hornschnorter@gmail.com>
cc: pgsql-hackers@postgreSQL.org
Subject: Re: Updated macOS start scripts
In-reply-to: <B55F452A-1579-4985-8D85-19FD50994399@gmail.com>
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>
 <3786.1511896652@sss.pgh.pa.us>
 <B55F452A-1579-4985-8D85-19FD50994399@gmail.com>
Comments: In-reply-to Mark Dilger <hornschnorter@gmail.com>
	message dated "Tue, 28 Nov 2017 11:57:41 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7562.1511901646.1@sss.pgh.pa.us>
Date: Tue, 28 Nov 2017 15:40:46 -0500
Message-ID: <7563.1511901646@sss.pgh.pa.us>
Precedence: bulk

Mark Dilger <hornschnorter@gmail.com> writes:
>> On Nov 28, 2017, at 11:17 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Hmm.  Maybe we should have the plist file set KeepAlive to false not true?
>> This would mean you'd need manual action to restart a failed postmaster,
>> but that probably comes with the territory --- I do not see how we'd
>> teach launchd the difference between a "failed" postmaster and a manually
>> shut down one.

> Setting KeepAlive to false does more than you probably want it to; it also
> causes the service not to start on boot nor on load.  After setting this to
> false, I tried a reboot and the service was not started.

I don't feel like digging in Apple's docs right now, but surely there's
some option that will make it start the service on boot, but not restart
it if it quits later?

> Of course, you could make pg_ctl know how to interact with launchctl if you
> like.  That seems quite hard, and I am not volunteering....

Seems like a nonstarter to me --- for one thing, how would pg_ctl know to
do that rather than its normal thing?  And where would it get the service
name?  And how's it gonna do that at all if not superuser?

			regards, tom lane