News for hackers. Stuff that matters.

A comment on Why Uber Engineering Switched from Postgres to MySQL. Parent comment

Re:Why Uber Engineering Switched from Postgres to MySQL by chucky_z on Tuesday July 26, 2016 @02:43PM (#12167863)
What replication issues are you referring too? I never once had a problem with pgsql's replication across 8.1->9.5.

It would randomly die, but that was always either my fault or the applications fault, never pgsql itself.

The lack of master-master seems to be the big thing everyone mentions, but PostgresXL is currently in a usable-in-production state.

[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL by tracker1 on Wednesday July 27, 2016 @05:22PM (#12176611)
But, what is the current replication setup that comes with postgres that is well documented with the PostgreSQL (current-version) documentation... the past, when I've looked there's mention of 2-3 solutions (none in-the-box) and others that require at least a 5-figure support contract.

Compare to MongoDB, RethinkDB, MS-SQL and others where the tooling for replication comes in the box. Yes, to of the examples are "no-sql" but even the mysql replication is in the box and supported as such.

[ Parent | on HN ]
Re:Why Uber Engineering Switched from Postgres to MySQL by chucky_z on Thursday July 28, 2016 @01:20AM (#12178461)
Did you read this?

https://www.postgresql.org/docs/current/static/high-availabi...

I'm not sure what more you can ask from documentation.

Does MySQL document Vitess, Galera, MaxScale, etc...?

[ Parent | on HN ]