3 ms·
Why not to migrate to the PostgreSQL which can handle more data and load than MySQL or MariaDB? It's also better at partitioning.
by xvilka 5y ago
Why not to migrate to the PostgreSQL which can handle more data and load than MySQL or MariaDB? It's also better at partitioning.
- smt88 5y agoI'm a huge Postgres fan, but... 1. Migrating is a huge, difficult, expensive project at Github's scale -- almost as bad as a rewrite 2. "Can handle more data and load" doesn't make sense as a blanket statement How much data and load Postgres can handle vs MySQL is determined by lots of variables. It's neither absolute nor consistent. It depends more on database and infrastructure design than on the underlying RDBMS. The best reason to choose Postgres over MySQL is not hardware efficiency but rather developer efficiency, although some projects get both.
- zip1234 5y ago"Changing the tires on a moving vehicle" but the moving vehicle is one of those road trains in Australia with 50 tires.
- WJW 5y agoWouldn't it actually get easier to move the tires on a vehicle with a lot of them? You can't change the tire on a unicycle while moving, but it would theoretically already be possible on a motorcycle if you can wheelie long enough (the back wheel is more difficult) and each wheel beyond that just adds more stability and redundancy.
- WatchDog 5y agoUber once chose to switch from postgres to mysql, for performance reasons. There was a lot of debate and discussion on HN[0] about it. I think there is enough complexity in either system, that you can't make generalizations that a given system can "can handle more data and load". [0]: https://news.ycombinator.com/item?id=26283348 https://news.ycombinator.com/item?id=26283348
- redis_mlc 5y agoThe reason was Postgres' write amplification issue, though I've read that has improved recently. Before a MySQL Innodb table could handle 20 indexes while Postgres around 5 with similar performance on updates.