vortipm.blogg.se - Homebrew install big sur

Homebrew install big sur how to#
Homebrew install big sur install#
Homebrew install big sur software#

Homebrew install big sur how to#

I’d love to learn more about how to debug Postgres installs.Install homebrew on mac m1. Hopefully, you see some of your own Postgres situation in my particular path, and you can hop on somewhere and get to your own solution. If I was just getting started or I didn’t care about losing that data, I likely would have blown everything away and run rails db:prepare and been up and running with Postgres 13. I went this route as I really wanted to hold on to the data I had in my local DBs.

Homebrew install big sur install#

I’m really unsure of what state the install is in, and it’s likely to trip me up in the future if I don’t handle it here while I have this context in my hed. I should remove it or otherwise plan on upgrading my app to it.

Postgres 13 is still installed on my machine.

With this, I could restart Rails and get my app up and running again. A quick start kicked the service off brew services start It’s important to note that even though I had linked brew to the old postgres version, when I was running brew commands, I still needed to reference the appropriate brew Postgres install, hence the Next Steps I began by checking which brew services were running with brew services list.

Running Postgresįinally, I had to restart Postgres. Checking the version through the terminal confirmed this. After fumbling with a few commands and various Stack Overflow posts, I discovered brew link -overwrite This pointed the postgres command at the latest version.

It was allowing both to be installed on my machine. Homebrew wasn’t installing the old version of Postgres over the existing 13.x. But checking the postgres version still returned the new Postgres install. brew install the old version my app was expecting onto my machine. Installing the older version of Postgres wasn’t too bad. 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. Bring my install up to the latest, 13.x or.Next, I check the version with postgres -version and I get back 13.x which is not the 12.x I expected. With a quick command in the terminal, which postgres, I see that it’s installed in /usr/local/bin which I know is where homebrew installs.

Homebrew install big sur 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.