I needed to install 12.x and then point homebrew at the install. The best way to do that would be to walk my local copy back to 12.x. I want to minimize the surface area and variables between known working versions of my software. I’m a believer in intentional upgrades and intentional changes.
#Osx brew install postgresql software#
In this case, I know that Postgres can be installed a number of different ways, and I want to verify how the software is installed. When I get stuck, I take a deep breath and gather up my assumptions. And which version of Postgres am I running?.Which install of Postgres am I running?.
I then when through my typical debugging questions: I rushed through my typical fix of deleting the postmaster.pid which usually gets left behind when my machine restarts only to find that this can cause worse problems when done incorrectly. Here’s my particular breadcrumb trail.Īfter starting my local Rails server after the OSX upgrade, I was greeted with the dreaded error “connection to database failed: could not connect to server: No such file or directory”. After flailing and staring at countless Stack Overflow threads, I found my way out of the woods. This is pretty typical for me after OS updates the feedback loop between updates is too long for my memory. I recently ran into an issue with Postgres after upgrading to Big Sur.
0 kommentar(er)
