![]() Some OS X users appear to use the PostgreSQL version built-in to OS X for their own data, rather than installing a new PostgreSQL. ![]() OS X built-in PostgreSQL deleted on update If you’re one of the ones who was using the built-in PostgreSQL, switch now. This was always the preferred option, and it’s what most users already did. Meanwhile, I strongly recommend that Apple users install their own PostgreSQL – Homebrew, Macports, Postgres.app or the EDB installer – and use that instead of Apple’s built-in PostgreSQL. I’ve also submitted a bug to Apple (#18719563) but don’t anticipate any action from that alone. So I can’t test most of this myself, and I really need reports from users, or if possible, results of proactive testing by OS X users. I don’t have access to a Mac because Apple’s policy prevents developers from running OS X for testing and development (or anything else) without buying physical Apple hardware and finding somewhere to run it. (Of course, you do that before any upgrade, but just in case it slipped your mind this time…). I can’t confirm anything yet, but back up all your databases before any upgrade to OS X 10.10. I’m seeing reports of a number of issues with PostgreSQL after upgrades of OS X machines to Yosemite (OS X 10.10) that I’m concerned about, so I’m seeking more information about the experiences of PostgreSQL users who’ve done OS X 10.10 upgrades.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |