Apple Removes MySQL From Lion Server

sfcrazy also noticed that Apple has officially removed MySQL from Lion Server, opting instead to include PostgreSQL, albeit in command line only form. The article speculates that the change is because MySQL is now Oracle property, and Apple is concerned about IP issues following all the legal issues surrounding Java.

MySQL can still be installed

[UnknowingFool]

To be clear, MySQL can be installed on Lion; it's just no longer installed by default.

Re:Samba has also been removed from server

[Henriok]

Apple stopped using SAMBA after SAMBA moved to GPL3 and Apple don't want to use such a license.

Installation of MySQL server on Mac OS X Lion

[psergiu]

http://www.djangoapp.com/blog/2011/07/24/installation-of-mysql-server-on-mac-os-x-lion/ [djangoapp.com]

1) Download the latest 64-Bit DMG Archive (Apple Disk Image) from MySQL Site (http://dev.mysql.com/downloads/mysql/). Current latest version is 5.5.14 which I’ll be using to install on my machine.
2) Mount the Disk Image (I mean open/double-click the DMG file) and install MySQL server by double-clicking the PKG file (in my case mysql-5.5.14-osx10.6-x86_64.pkg) and follow onscreen instructions. ( It will ask for Master password, as it installs MySQL server in /usr/local )
3) Add /usr/local/mysql/bin to your path by editing .profile file. (Optionally you can create alias to mysql and mysqladmin as mentioned in README File)
4) You can start MySQL server by running “/usr/local/mysql/bin/mysqld_safe &” from terminal but Disk image you downloaded also consists of Startup Package & Preferences Pane which allows you to start/stop MySQL server from System Preferences and even Automatically Start MySQL Server at Startup.

Re:Samba has also been removed from server

[CharlyFoxtrot]

It's not prebuilt but Macports [macports.org] has ports for samba 3.2.15 and samba 4.0.0tp5. Installing from Macports isn't difficult for anyone with a modicum of unix savvy.

Re:Much better anyway

[Anonymous Coward]

pgAdmin3 [pgadmin.org] is the way to go, it works really well and pretty much has a "just give me a damn database" button.

I started with PostgreSQL and had to use MySQL for some projects later. I find MySQL and its tools to be cumbersome, but that's likely just due to my familiarity with PostgreSQL.

Re:Much better anyway

[fuzzytv]

Not true. Manual vacuuming is not needed since PostgreSQL 8.1, released 2005/11, that's almost 6 years ago. The functionality is called 'autovacuum" and it's fully automatic so you don't need to care about it anymore, and it was significantly improved in the following versions. In some cases you have to tune it a bit (to make it more aggresive for example), but in 99% it works fine out of the box.

Maybe your site was one of those 1% that needed a bit more tuning, or maybe changes at the application level (not everything that works on one database will work fine one another one). Otherwise it's a pure FUD. We're running a lot of applications (with a lot of write activity) on PostgreSQL, and it works perfectly.

Sure, nothing is perfect - for example the memory management is not perfect, you need a bit of experience when setting the memory limits. But I really don't think "leaking to disk" is the right term. You can set 'maintenance_work_mem' and if the process needs more, it has to put that on disk. But with reasonable limit and autovacuum that really does not happen.