News for hackers. Stuff that matters.
Re:Plans for partitioning in PostgreSQL v11 by grogers on Tuesday August 15, 2017 @07:49AM (#15017293)
It might be a good choice to switch to postgres, but it isn't like MySQL isn't innovating too. 8.0 will have a ton of features. This includes a bunch of "catch up" things like CTEs and SKIP LOCKED, but also stuff like synchronous replication built in.
Re:Plans for partitioning in PostgreSQL v11 by jimktrains2 on Tuesday August 15, 2017 @11:08AM (#15018904)
I know the defaults have been changed to be safe, but I will forever feel like my trust was broken with MySQL the day I learned how bad the defaults are. Not just inefficent/generic, but actually bad.

Additionally, I feel that postgresql is better engineered, more featureful, and has support for a much larger variety of use-cases (e.g. hstore, json, postgis, pg-routing, uuids, trigram indecies, &c). So between engineering perks, and the loss of trust, I only use MySQL in legacy applications that I cannot port.

Re:Plans for partitioning in PostgreSQL v11 by rhaas on Tuesday August 15, 2017 @09:54AM (#15018154)
The first release of PostgreSQL that had synchronous replication was released in September 2011.

https://www.postgresql.org/docs/9.1/static/release-9-1.html