Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
"No binaries" after installing the multi-version Postgres.app on OS X #595
Comments
|
Non-obvious via error message or documentation, but the solution is to use the sidebar button to create a new server (of whichever version you want), then click the initialize button on the right to initialize the server. This issue was very helpful: #399 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Had an OS X system running Postgres 9.2. Installed multi-version Postgres.app from the dmg and when I ran the app, it displayed the control screen, showed Postgres 9.2 as available, but with the message "no binaries". While that may have referred to the fact that the multi-version app did not have 9.2 binaries, that wasn't clear. I could not install any of the versions available in the app until I removed the 9.2 version. Then I was able to install and activate 10.0 (I didn't try the others, but I presume it would have worked with those as well).
If the "no binaries" message referred to 9.2, then the message should have been worded to make that clear. As it was it looked like it was saying it didn't know where to find any of the binaries.
If I needed to remove 9.2 before I installed any of the binaries from the new version, that should have been documented somewhere. I followed the "how to update" instructions, which worked very well except for this issue -- the pgdumpall followed by the restore procedure worked flawlessly.