| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mark Dilger <hornschnorter(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Updated macOS start scripts |
| Date: | 2017-11-28 21:22:02 |
| Message-ID: | b6a8fcda-fe25-cde8-11ac-1a5fed95fbc0@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-11-28 21:23:11 | Re: pgindent run? |
| Previous Message | Robert Haas | 2017-11-28 21:06:21 | Re: [HACKERS] postgres_fdw super user checks |