postgreSQL broken fatally with Server 3.2.1

Question

Level 1

14 points

postgreSQL broken fatally with Server 3.2.1

Apple Gurus - the Server 3.2.1 update really and truly breaks postgreSQL - can any of you software superstars that work for Apple please help get this fixed?

Posted on Sep 18, 2014 8:38 PM

Reply

Answer 1

Sep 19, 2014 12:07 AM in response to TonyPHX_623

It's difficult to say what might be wrong from your description. 😉 However, Server 3.2.1 upgraded PostgreSQL from 9.2.x to 9.3.x, and one of the configuration keys changed (from "unix_socket_directory" to "unix_socket_directories"). You might need to make sure and old configuration files are updated to use unix_socket_directories. You only need to change the key, the value can stay exactly the same.

Reply

Answer 2

TonyPHX_623 Author

Level 1

14 points

Sep 19, 2014 6:40 AM in response to mscott_mdm

I agree with the defect that you note, but one other observation I have made...

If you do a clean install of Mavericks and Server, they have dramatically changed the PostgreSQL directory structure. What we have seen from a migration standpoint is totally different than a clean install as far as form and function.

I built a system from scratch and found it easier to just deploy PostgreSQL myself rather than use the Apple provided(?) PostgreSQL. Seriously, try it and check it out, it is eye opening.

Reply

Answer 3

Sep 20, 2014 11:37 AM in response to TonyPHX_623

This is very much why I installed MySQL for anything that doesn't depending on Apple PSQL.

1) In my experience, it is easier to find support for MySQL.

2) If you like there are some good GUI tools for it.

3) Most importantly, I control when the service is upgraded rather than it being included in a global service update.

Reply