Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
I read from a post about comparing MySQL and PostgreSQL, there is one who said:
The biggest disadvantage of PG for me had been the lack of replication, but it's recently gotten both asynchronous and synchronous replication.
Source: https://www.quora.com/What-are-pros-and-cons-of-PostgreSQL-and-MySQL
So my question is: What does that "PostgreSQL lacks replication" mean?
It means nothing, really. PostgreSQL has a number of replication features, as the relevant chapter in the manual details.
That article is apallingly wrong and outdated. Ignore it. "No referential integrity" in MySQL? Bah.
If you have an account on that site, please ask for it to be removed or fixed or whatever can be done. As it stands it's dangerously misleading and wrong, and has no place claiming to be current accurate information.
I'm not going to read that article. Replication is the ability to create a copy of itself as you'll see for backup/disaster-recovery or for distributed systems, such as a CDN.
Synchronous vs Asynchronous is how that backup is performed. Synchronous keeps all databases in sync. Asynchronous queues updates, which means if the primary server goes down before data is transferred, you might have data loss.
There are a number of replication features, such as load balancing or connection pooling. Postgres may not have them all, but it has a decent amount (there are 3rd party tools for what can't be satisfied by the native application).
There's a chance whatever you read was comparing older versions of both MySQL and PostgreSQL. However, you can always see more information about Postgres features in its wiki.
