I then compared the pgconfig output of homebrew and Postgres.app. Would moving postgres's launchd plist to /Library/LaunchDaemons/ be a better idea? It would potentially make postgres and apache be shut down at the same time, which given 20 seconds to stop should be enough time for postgres to exit cleanly. Postgres.app is slow even when it uses the C locale. Which means postgres gets SIGKILLed and leaves it's postmaster.pid file lying around which prevents postgres from starting up the next boot until I rm that file.
#POSTGRES APP VS HOMEBREW INSTALL#
Homebrew users can just run brew install postgis and tends to be a favorite for more.
#POSTGRES APP VS HOMEBREW UPGRADE#
I specifically remember a particular postgres upgrade via homebrew went wrong and I had to basically erase all traces of postgres before re-installing again in order to get it to work. And apache doesn't shutdown until the system is shutting down. OSX A popular distribution particularly for newbies is Postgres. In my limited experience (no longer using macOS after 6 years on the platform), homebrew upgrades was broken more often than upgrades provided by GUI applications.
The problem is that the sessions are owned by the rails apps running under passenger and therefore won't shut down until apache shuts down. Basically Launchd sends SIGTERM to every user process and then 20 seconds later ( ) sends SIGKILL, but postgres treats SIGTERM as a "smart shutdown" signal ( ) and waits for all it's existing sessions to close themselves before quitting. Open up the Terminal and install postgresql with brew: brew install postgresql You may see instructions on the web reading brew install postgres instead of postgresql both options will install PostgreSQL on your computer. That is just an extra painful step that takes up more time to execute. This is because Postgres.app can’t start when another server is already running on the same port. The beautiful thing about a Homebrew install is that you can simply use your native Terminal window you use for controlling your machine instead of the Sql shell that comes with the install. if you previously installed PostgreSQL with Homebrew). I have several rails apps that use postgres which are managed by passenger which in turn is managed by apache.Ĭurrently apache is started by launchd at boot from /System/Library/LaunchDaemons/, apache starts passenger via /etc/apache2/other/nf and once I've logged in postgres is started via ~/Library/LaunchAgents/.Įverything starts fine and works great until I need to shut down or reboot my mac then I run into a problem with how launchd tears down everything. In either case, a solution I found is that you need to uninstall other PostgreSQL installations (i.e. I have postgres and passenger installed from homebrew, and use the os x built in apache.
0 kommentar(er)
